gmane.editors.winedt

Display problem toward end of document

Hi,

I have the following problem:

replacing the whole content of a file with a much shorter one (via ctrl+A
followed by ctrl+V), when the last page of the original document was
displayed, as result I only see the last line of the pasted text and the
rest of the window empty.
On my opinion, at this point the last page of the pasted text should be
displayed.

Is this due to some settings or this feature is not planned?

Thanks for any hint,

Daniele

headers

WinEdt Team | 10 May 00:27

Re: Display problem toward end of document

> I have the following problem:
>
> replacing the whole content of a file with a much shorter one (via ctrl+A
> followed by ctrl+V), when the last page of the original document was
> displayed, as result I only see the last line of the pasted text and the
> rest of the window empty.
> On my opinion, at this point the last page of the pasted text should be
> displayed.
>
> Is this due to some settings or this feature is not planned?

WinEdt avoids resizing Vertical Scrolling unless absolutely
necessary because doing so results in flickering and can be
confusing as the text jumps on the screen. However, in this
(and similar cases) the result is indeed a bit odd and it would
much more natural if the last line was at the bottom of the
screen rather than on the top.

This has now been fixed for the next version. It's not really a
problem (more an oddity)...

Also, I've spent the afternoon introducing a few filters that
prevent unwanted activation of active strings with wildcards.
This, too, will be addressed in the next version. Patience:
more time consuming and problematic work on the new console is
still pending...

Best regards,

alex

(Continue reading)

headers

Benatzky, Joachim | 10 May 14:15

Wrapping commented lines

Hi Alex,

Thanks for the new release that I like!

But I'm puzzled about wrapping: It seems to me that the wrapping
behaviour of commented lines has changed in WinEdt 5.6 beta1. In WinEdt
5.5 commented (%; right mouse click --> 'Insert Commment') lines were
also wrapped but now they are not. I think that I use the same settings
(soft wrapping / comments enabled) as before and normal text is wrapped.

Cheers,

Joachim.

headers

WinEdt Team | 10 May 23:07

Re: Wrapping commented lines

> Thanks for the new release that I like!
>
> But I'm puzzled about wrapping: It seems to me that the
> wrapping behaviour of commented lines has changed in WinEdt 5.6
> beta1. In WinEdt 5.5 commented (%; right mouse click -->
> 'Insert Commment') lines were also wrapped but now they are
> not. I think that I use the same settings (soft wrapping /
> comments enabled) as before and normal text is wrapped.

Options -> Advanced -> Environments

Change

WRAP_SOFT_COMMENTS=0 // Do not Wrap Comments in Soft Mode!

to

WRAP_SOFT_COMMENTS=1 // Wrap Comments in Soft Mode!

and reload the modified from from the same menu (or restart
WinEdt).

Best regards,

alex

headers

Jonathan Ostroff | 12 May 21:31

Winedt 5.6/TexLive2007/dviout

I am using the Texlive 2007 (have uninstalled miktex). When I generate DVI I
now get a program called DVIOUT.

Is there a way to get reverse search from the dvi output back to the latex
files in winedt?

Thanks

Jonathan

headers

Hector C | 13 May 00:18

Re: Winedt 5.6/TexLive2007/dviout

Jonathan Ostroff wrote:
> Is there a way to get reverse search from the dvi output back to the latex
> files in winedt?

src=<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program 
Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"

I am not sure whether the above command is redundant (DDEServer and 
command line), but it works for me, just be sure that the registry (see 
below) and the parameter file don't conflict.

Cheers,

Hector C.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SHIMA\DVIOUT\Settings]
"src"="<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\\Program 
Files\\WinEdt\\WinEdt.exe^s\"[Open(|%s|);SelPar(%d,8);]\""

headers

Jonathan Ostroff | 13 May 03:21

RE: Re: Winedt 5.6/TexLive2007/dviout

Thanks for this information. Where do I go to insert these instructions. 

Is it Options --> Execution Modes?

Thanks

Jonathan

> -----Original Message-----
> From: news [mailto:news <at> ger.gmane.org] On Behalf Of Hector C
> Sent: Monday, May 12, 2008 6:18 PM
> To: winedt+list <at> wsg.net
> Subject: [WinEdt] Re: Winedt 5.6/TexLive2007/dviout
> 
> Jonathan Ostroff wrote:
> > Is there a way to get reverse search from the dvi output back to the
> latex
> > files in winedt?
> 
> src=<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program
> Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"
> 
> I am not sure whether the above command is redundant (DDEServer and
> command line), but it works for me, just be sure that the registry (see
> below) and the parameter file don't conflict.
> 
> Cheers,
> 
> Hector C.
>

(Continue reading)

headers

Hector C | 14 May 21:39

Re: Winedt 5.6/TexLive2007/dviout

Jonathan Ostroff wrote:
> Thanks for this information. Where do I go to insert these instructions. 
> 
> Is it Options --> Execution Modes?

In dviout: options->Setup Parameters->Common->src type
<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program 
Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"

or include
src=<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program 
Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"

in the configuration file. Make sure that the registry doesn't have a 
different command. For more information, read

http://magic.aladdin.cs.cmu.edu/2007/03/06/switching-from-yap-to-dviout/

Cheers,

Hector C.

headers

Jonathan Ostroff | 14 May 22:01

RE: Re: Winedt 5.6/TexLive2007/dviout

Dear Hector:

Thanks for the help. It is now working.

Jonathan

> -----Original Message-----
> From: news [mailto:news <at> ger.gmane.org] On Behalf Of Hector C
> Sent: Wednesday, May 14, 2008 3:40 PM
> To: winedt+list <at> wsg.net
> Subject: [WinEdt] Re: Winedt 5.6/TexLive2007/dviout
> 
> Jonathan Ostroff wrote:
> > Thanks for this information. Where do I go to insert these
> instructions.
> >
> > Is it Options --> Execution Modes?
> 
> 
> In dviout: options->Setup Parameters->Common->src type
> <`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program
> Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"
> 
> or include
> src=<`WinEdt DDEServer [Open('%s');SelPar(%d,8);]`c:\Program
> Files\WinEdt\WinEdt.exe^s"[Open(|%s|);SelPar(%d,8);]"
> 
> in the configuration file. Make sure that the registry doesn't have a
> different command. For more information, read
>

(Continue reading)

headers

Benatzky, Joachim | 18 May 23:21

AW: Wrapping commented lines

Hi Alex,

Thanks you for your help!

Didn't get it immediatelty, but now it works as I want!

Cheers,

Joachim.

> -----Ursprüngliche Nachricht-----
> Von: WinEdt Team [mailto:support <at> winedt.com] 
> Gesendet: Samstag, 10. Mai 2008 23:07
> An: winedt+list <at> wsg.net
> Betreff: Re: [WinEdt] Wrapping commented lines
> 
> > Thanks for the new release that I like!
> >
> > But I'm puzzled about wrapping: It seems to me that the wrapping 
> > behaviour of commented lines has changed in WinEdt 5.6 beta1. In 
> > WinEdt 5.5 commented (%; right mouse click --> 'Insert Commment') 
> > lines were also wrapped but now they are not. I think that 
> I use the 
> > same settings (soft wrapping / comments enabled) as before 
> and normal 
> > text is wrapped.
> 
> Options -> Advanced -> Environments
> 
> Change

(Continue reading)

headers

Cao, Xiaochun | 13 May 15:42

Unsubscribe request

-----Original Message-----
From: WinEdt Team [mailto:support <at> winedt.com] 
Sent: Friday, May 09, 2008 6:28 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Display problem toward end of document

> I have the following problem:
>
> replacing the whole content of a file with a much shorter one (via 
> ctrl+A followed by ctrl+V), when the last page of the original 
> document was displayed, as result I only see the last line of the 
> pasted text and the rest of the window empty.
> On my opinion, at this point the last page of the pasted text should 
> be displayed.
>
> Is this due to some settings or this feature is not planned?

WinEdt avoids resizing Vertical Scrolling unless absolutely necessary
because doing so results in flickering and can be confusing as the text
jumps on the screen. However, in this (and similar cases) the result is
indeed a bit odd and it would much more natural if the last line was at
the bottom of the screen rather than on the top.

This has now been fixed for the next version. It's not really a problem
(more an oddity)...

Also, I've spent the afternoon introducing a few filters that prevent
unwanted activation of active strings with wildcards.
This, too, will be addressed in the next version. Patience:

(Continue reading)

headers

WinEdt Team | 13 May 16:12

Re: Unsubscribe request

Yes we are all troubled and put-out by unwanted mails.

It majorly helps if one would read (and remember) the guidelines, which 
include:

 To unsubscribe from the WinEdt Mailing List, send an empty  mail  to:
   <winedt+list-unsubscribe <at> wsg.net>  from  the  account  that  you  are
   subscribed with.

   DO NOT send a mail to the list! This will have no effect  apart  from
   annoying the subscribers.

regards
 Adriana

----- Original Message ----- 
From: "Cao, Xiaochun" <XCao <at> ObjectVideo.com>
To: <winedt+list <at> wsg.net>
Sent: Tuesday, May 13, 2008 10:42 AM
Subject: [WinEdt] Unsubscribe request

-----Original Message-----
From: WinEdt Team [mailto:support <at> winedt.com]
Sent: Friday, May 09, 2008 6:28 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Display problem toward end of document

> I have the following problem:
>
> replacing the whole content of a file with a much shorter one (via

(Continue reading)

headers

Olli J. Marttila | 1 May 21:10

Re: ANN: WinEdt 5.6

WinEdt Team kirjoitti:
> Beta version of WinEdt 5.6 is now available for testing.
> 
> Read the instructions carefully and proceed accordingly. You
> should also read the What's New section for description of all
> the changes, bug fixes, etc...
> 
> This version may not be for everyone: Macros in Exec folder
> have been rewritten and the Accessories Menu for MiKTeX and TeX
> Live has been changed to call the new (common) macros that can
> execute console applications in WinEdt's Console. Restoring the
> old macros in Exec folder or the old Accessories Menu will not
> (can not!) work properly with the new Execution Modes...
> 
> Documentation is yet to be updated: reading the What's New
> file is the only way to get familiar with the new
> functionality.
> 
> Have fun.
> 
> Best regards,
> 
> alex
> 

Two comments:

1) After installing WinEdt56 beta1 the insert key does not 
change between Insert/Overstrike anymore.
2) Texify does not produce a pdf file; I have now go path

(Continue reading)

headers

David Huffer | 1 May 21:17

RE: ANN: WinEdt 5.6

Olli J. Marttila wrote:
> 1) After installing WinEdt56 beta1 the insert key does not
> change between Insert/Overstrike anymore.

I cant confirm this at least when switching modes from the status line.

> 2) Texify does not produce a pdf file; I have now go path
> texify > dvi > dvi2pdf - or is this a MiKTeX error (MiKTeX
> updated April 30).

--

-- 
 David

headers

WinEdt Team | 2 May 00:25

Re: ANN: WinEdt 5.6

> Olli J. Marttila wrote:
> > 1) After installing WinEdt56 beta1 the insert key does not
> > change between Insert/Overstrike anymore.
>
> I cant confirm this at least when switching modes from the
> status line.

Options -> Configuration Wizard | Options: You can choose what
you want the Insert key to do. I don't like switching Insert/
Overwrite because working on different laptops for testing
purposes I often accidentally press the Insert Key on a
keyboard that is not familiar to me (no two are the same). My
personal preference accidentally ended up in the default
settings and this will be corrected: it is just a matter of
choosing an option in the Wizard...

And of course, nothing like this is hard coded: Shortcuts can
be customized though the Menu Setup Dialog to do anything one's
heart might desire

> 2) Texify does not produce a pdf file; I have now go path
> texify > dvi > dvi2pdf - or is this a MiKTeX error (MiKTeX
> updated April 30).

Nothing has changed here except for the layout and contents of
the default toolbar (as described in What's New). By default
TeXify calls texify.exe (without --pdf switch) and as such it
usually produces dvi file (just like before). PDFTeXify
produces pdf and by default the "universal" Compile command
(the first TeX Button in the toolbar) is also configured to

(Continue reading)

headers

Olli J. Marttila | 2 May 23:20

Re: ANN: WinEdt 5.6

WinEdt Team kirjoitti:
>> Olli J. Marttila wrote:
>> > 1) After installing WinEdt56 beta1 the insert key does not
>> > change between Insert/Overstrike anymore.
>>
>> I cant confirm this at least when switching modes from the
>> status line.
> 
> Options -> Configuration Wizard | Options: You can choose what
> you want the Insert key to do. I don't like switching Insert/
> Overwrite because working on different laptops for testing
> purposes I often accidentally press the Insert Key on a
> keyboard that is not familiar to me (no two are the same). My
> personal preference accidentally ended up in the default
> settings and this will be corrected: it is just a matter of
> choosing an option in the Wizard...
> 
> And of course, nothing like this is hard coded: Shortcuts can
> be customized though the Menu Setup Dialog to do anything one's
> heart might desire
> 
>> 2) Texify does not produce a pdf file; I have now go path
>> texify > dvi > dvi2pdf - or is this a MiKTeX error (MiKTeX
>> updated April 30).
> 
> Nothing has changed here except for the layout and contents of
> the default toolbar (as described in What's New). By default
> TeXify calls texify.exe (without --pdf switch) and as such it
> usually produces dvi file (just like before). PDFTeXify
> produces pdf and by default the "universal" Compile command

(Continue reading)

headers

Evan Cooch | 1 May 21:29

Re: ANN: WinEdt 5.6


>
> 2) Texify does not produce a pdf file; I have now go path texify > dvi 
> > dvi2pdf - or is this a MiKTeX error (MiKTeX updated April 30).

It never did by default - it generated a DVI, and spawned yap.

headers

Olli J. Marttila | 1 May 21:39

Re: ANN: WinEdt 5.6

Olli J. Marttila kirjoitti:
> WinEdt Team kirjoitti:
>> Beta version of WinEdt 5.6 is now available for testing.
>>
>> Read the instructions carefully and proceed accordingly. You
>> should also read the What's New section for description of all
>> the changes, bug fixes, etc...
>>
>> This version may not be for everyone: Macros in Exec folder
>> have been rewritten and the Accessories Menu for MiKTeX and TeX
>> Live has been changed to call the new (common) macros that can
>> execute console applications in WinEdt's Console. Restoring the
>> old macros in Exec folder or the old Accessories Menu will not
>> (can not!) work properly with the new Execution Modes...
>>
>> Documentation is yet to be updated: reading the What's New
>> file is the only way to get familiar with the new
>> functionality.
>>
>> Have fun.
>>
>> Best regards,
>>
>> alex
>>
> 
> Two comments:
> 
> 1) After installing WinEdt56 beta1 the insert key does not change 
> between Insert/Overstrike anymore.

(Continue reading)

headers

Ferdinand Fichtner | 2 May 13:44

Re: ANN: WinEdt 5.6

Thanks, Alex!

 > Beta version of WinEdt 5.6 is now available for testing.

One little thing I noticed: If I use my mouse's scroll wheel in the new 
Winedt console, it does not scroll the displayed output but instead 
strangely moves the text around: If scrolling the wheel upwards, the 
text is slowly shifted upwards (instead of line-by-line downwards), the 
resulting gap at the lower edge of the console being filled with white 
space.

This is Winedt 5.6 running on Windows XP (SP3) with a simple USB 
Logitech mouse using Microsoft's standard mouse driver.

If you need more information about the problem, I a glad to help.

Regards! Ferdinand

headers

David Huffer | 2 May 17:30

RE: ANN: WinEdt 5.6

On Friday, May 02, 2008 7:45, Ferdinand Fichtner wrote:

 > ...If I use my mouse's scroll wheel  in  the
 > new  Winedt  console, it does not scroll the
 > displayed output but instead strangely moves
 > the text around...

I notice the same behavior with logitech optical mouse.

--
 David

headers

WinEdt Team | 2 May 23:38

Re: ANN: WinEdt 5.6

> One little thing I noticed: If I use my mouse's scroll wheel in
> the new Winedt console, it does not scroll the displayed output
> but instead strangely moves the text around: If scrolling the
> wheel upwards, the text is slowly shifted upwards (instead of
> line-by-line downwards), the resulting gap at the lower edge of
> the console being filled with white space.
>
> This is Winedt 5.6 running on Windows XP (SP3) with a simple
> USB Logitech mouse using Microsoft's standard mouse driver.
>
> If you need more information about the problem, I a glad to
> help.

I dusted off my old Logitech USB mouse and tried to scroll in the
console. You are right, the custom scroll wheel response does not
work properly. This has now been fixed for the next version (easy
once it is reproduced).

If you disable the option "Custom Wheel Response" in the
Preferences| Shell Dialog the problem with scrolling inside the
console will go away but you will likely lose the ability to
use the wheel in the edit window. Thus this is not really a
solution but just in case it would help if you can confirm...

Best regards,

alex

headers

David Huffer | 2 May 23:32

RE: ANN: WinEdt 5.6

On Friday, May 02, 2008 5:39, WinEdt Team wrote:

 > ...If you disable the option  "Custom  Wheel
 > Response"  in  the Preferences| Shell Dialog
 > the   problem   with  scrolling  inside  the
 > console will go away  but  you  will  likely
 > lose  the  ability  to  use the wheel in the
 > edit window.  Thus  this  is  not  really  a
 > solution  but  just in case it would help if
 > you can confirm...

Yes, disabling the custom wheel response does indeed allow
wheel-scrolling within the console.

Also, i just noticed that when focus is in the console and i
issue "ctrl-shift-L" that for some reason an itemized list
begins to iterate in the console. It start with a bullet which
is then replaced with a '1' then 'a' then 'A' and so on each
time i re-issue the keys. BTW, I have "ctrl-shift-L" bound to
&AccessoriesMine|&LaTeX, which of course i'm not using anymore.

--
 David

headers

WinEdt Team | 3 May 00:31

Re: ANN: WinEdt 5.6

> Yes, disabling the custom wheel response does indeed allow
> wheel-scrolling within the console.

As I suspected. This will no longer be required in the next
version...

> Also, i just noticed that when focus is in the console and i
> issue "ctrl-shift-L" that for some reason an itemized list
> begins to iterate in the console. It start with a bullet which
> is then replaced with a '1' then 'a' then 'A' and so on each
> time i re-issue the keys. BTW, I have "ctrl-shift-L" bound to
> &AccessoriesMine|&LaTeX, which of course i'm not using anymore.

When Console has focus all keyboard input is passed to the
Console and WinEdt's Menu Shortcuts don't work.

WinEdt does intercept ESC Key (which de-focuses the console) and
Ctrl+Shift+C (which hides it). As for the rest the default Windows
Shortcuts for Rich Edit Control apply. For example Ctrl+L and
Ctrl+R change bi-di settings (left to right or right to left).
Ctrl+Shift+L appears to insert items that would be used in List
but this is not done by WinEdt. Actually Windows WordPad (which
provides an interface to Rich Edit Control) responds to the
shortcut Ctrl+Shift+L exactly the same was as WinEdt's Console as
it should since WinEdt does not attempt to change this control's
behavior...

I see no point in suppressing Windows Shortcuts in the console
(note that moving with arrows or Page up/Down etc... is also
left to console rather than WinEdt). What you must know: when

(Continue reading)

headers

RS | 6 May 18:35

Re: ANN: WinEdt 5.6

Hi Alex,

> WinEdt 5 [Build 20080429 (v. 5.6)] (Beta 1)
> ===========================================

>   Console 

The Console is really nice! Some issues, though:

* It somewhat flickers (harmless, but makes it look a bit 'fragile'...)

* Is there no other way than to use Rich Edit Control? The console could 
be enhanced quite a bit if the command prompt shortcuts like TAB for 
file name completion or the Arrows for walking through the command 
history or CTRL-C for cancel worked. Also, the oddities with CTRL-L and 
other shortcuts wouldn't arise.

* I've tried to run a cygwin shell in the Console but the text is 
somehow garbled (also connected to REC?). What would look like this in a 
normal command window:
--------------------------------------------
schlcht <at> SCHLCHT ~
$ pwd
/home/schlcht

schlcht <at> SCHLCHT ~
$
--------------------------------------------
is turned into:
--------------------------------------------

(Continue reading)

headers

WinEdt Team | 9 May 19:04

Re: ANN: WinEdt 5.6

> The Console is really nice! Some issues, though:

I am not particularly happy with using Edit or RichEdit control
for console I/O but these were the only two (almost)
ready-to-use controls in Delphi. I may have to rethink this
although I would be a bit reluctant doing it from scratch...

> * It somewhat flickers (harmless, but makes it look a bit 'fragile'...)

Delphi controls are notorious for this kind of extra refreshing. I
will likely end up abandoning REC and replace it with a custom
one.

> * Is there no other way than to use Rich Edit Control? The console could
> be enhanced quite a bit if the command prompt shortcuts like
> TAB for file name completion or the Arrows for walking through
> the command history or CTRL-C for cancel worked. Also, the
> oddities with CTRL-L and other shortcuts wouldn't arise.

I tried to generate CTRL_C_EVENT in response to Ctrl+C but it
does not work. There may be a way around with some effort. The
rest again means that a different control (with different
custom programmed responses) should be used or else a custom
event handler implementing alternative responses and
suppressing the unwanted ones should be implemented. This means
custom programming or finding a third party control that
already does that (I am not aware of any)...

> * I've tried to run a cygwin shell in the Console but the text is
> somehow garbled (also connected to REC?). What would look like

(Continue reading)

headers

RS | 14 May 02:34

Re: ANN: WinEdt 5.6

On 09.05.2008 19:04, WinEdt Team wrote:
> I am not using cygwin but I would suggest that you check if it
> can be started with some switch to suppress echo or at least
> suppress VT100 ESC sequences. For example, Windows Command
> Prompt should be started with
> 
> cmd.exe /Q
> 
> to avoid double-echo in WinEdt's Console.
> 
> How does cygwin shell perform in standard Windows Console (or
> does it start its own Window)?

It uses a standard Windows console (maybe with its own driver?). In the 
meantime, I found out that the escape sequences are supposed to set some 
fancy colors, so by changing the prompt to something simple (">"), I 
could at least improve the situation in that I don't get garbage on each 
line anymore. Every input line is still doubled (didn't find a way to 
avoid double-echo, if that's what it is), but that's something I can 
live with.

>> * Could `Copy to Clipboard' not be made to work while the application is
>> still running? Also, text can be selected, but the selection
>> immediately disappears again, so you cannot copy manually,
>> either.

...and pasting into the console (using the paste button) doesn't really 
work, either: although the pasted text appears in the console, the 
applications don't see it.

(Continue reading)

headers

WinEdt Team | 27 May 02:22

Re: ANN: WinEdt 5.6

Robert,

> > I am not using cygwin but I would suggest that you check if it
> > can be started with some switch to suppress echo or at least
> > suppress VT100 ESC sequences. For example, Windows Command
> > Prompt should be started with
> >
> > cmd.exe /Q
> >
> > to avoid double-echo in WinEdt's Console.
> >
> > How does cygwin shell perform in standard Windows Console (or
> > does it start its own Window)?
>
> In the meantime, I found out that the escape sequences are
> supposed to set some fancy colors, so by changing the prompt to
> something simple (">"), I could at least improve the situation
> in that I don't get garbage on each line anymore. Every input
> line is still doubled (didn't find a way to avoid double-echo,
> if that's what it is), but that's something I can live with.

In other words: out with the RichEdit control; in with a few K
lines of custom code to emulate more standard console behavior.

Done.

This should address most of the problems you experienced with
the console (refreshing, focus, arrows, queued input buffer,
pasting, and echo).

(Continue reading)

headers

RS | 27 May 03:02

Re: ANN: WinEdt 5.6

On 27.05.2008 02:22, WinEdt Team wrote:
> In other words: out with the RichEdit control; in with a few K
> lines of custom code to emulate more standard console behavior.
> 
> Done.

 You're ace!

--

-- 
  Robert

headers

Gyorgy SZEIDL | 9 May 11:37

WinEdt 5.6 -- texify does not work

to whom it may concern,

i have just installed winedt 5.6 beta 1. when installing it i
followed your instructions.

my pervious installation was put into the directories

c:\wined55

and

c:\Documents and Settings\Application Data\Gyorgy\Winedt

when installing the beta version:

1. i did not change the name of the directory

c:\wined55

2. i renamed the directory

c:\Documents and Settings\Application Data\Gyorgy\Winedt

to

c:\Documents and Settings\Application Data\Gyorgy\Winedt55.

3. i installed the beta version into the directories

c:\wined56

(Continue reading)

headers

WinEdt Team | 9 May 19:05

Re: WinEdt 5.6 -- texify does not work

> i have just installed winedt 5.6 beta 1. when installing it i
> followed your instructions.
>
> etc...
>
> i restarted winedt end restored my old settings
>
> everything seemed to be ok. however when i wanted to texify one of my
> projects
> i got an error message:
>
> missing texify.edt in the directory:
>
> c:\Documents and Settings\Application Data\Gyorgy\Winedt\exec\miktex
>
> what have i done wrong?

You restored ALL (or shall I say too many!) of your old
settings. The new Accessories Menu has been changed and the old
items will not work. MiKTeX and TeX Live now both use the same
macros in Exec\TeX folder (this means half the work for me
maintaining two sets of macros). Even if you would manually
copy this missing macro file you would not be getting the new
functionality with console and improved execution modes...

Options -> Maintenance -> Default and restore at least the new
Accessories Menu (toolbar, too, may have to be manually
modified if you want to use the old one and some other menus
have been slightly modified as well). Re-loading Options ->
Configurations -> MiKTeX might fix the problem as well unless

(Continue reading)

headers

Gyorgy SZEIDL | 11 May 09:34

Re: WinEdt 5.6 -- texify does not work

dear alex,

thank you for your recommendations.
i did as i had been recommended. now everything works
fine. thank you once again.
best regards

gyorgy
>> i have just installed winedt 5.6 beta 1. when installing it i
>> followed your instructions.
>>
>> etc...
>>
>> i restarted winedt end restored my old settings
>>
>> everything seemed to be ok. however when i wanted to texify one of my
>> projects
>> i got an error message:
>>
>> missing texify.edt in the directory:
>>
>> c:\Documents and Settings\Application Data\Gyorgy\Winedt\exec\miktex
>>
>> what have i done wrong?
>
> You restored ALL (or shall I say too many!) of your old
> settings. The new Accessories Menu has been changed and the old
> items will not work. MiKTeX and TeX Live now both use the same
> macros in Exec\TeX folder (this means half the work for me
> maintaining two sets of macros). Even if you would manually

(Continue reading)

headers

Gyorgy SZEIDL | 11 May 14:28

winedt 5.6 -- what i miss

dear alex and list members,

winedt 5.6 has changed a lot. some of the changes are however
negative ones.

1. when editing a book (each chapter is in a separate file) i use the dvi
search icon (direct search or dvi search) to jump from the latex file to 
the
place i am interested in in my dvi file. this icon is not available 
anymore in
the main window. it is offered to you in the menu accessories with the name
dvi search. if i want to reach it i have to click twice. it is much 
simpler to
do that it in the traditional way, that is by using the icon that is 
available in
the main menu in winedt 5.5. the lack of this icon in the main menu is a 
serious
drawback for me. (i have been  working on a textbook for a year and this 
feature
helps me when making corrections.)

2. i have no idea how to make a pdf file from a traditional TeX file. in
version 5.5 there are some icons to make a pdf file from a TeX file.
this issue seems to be is unresolved since these icons are missing not
only in the main menu but from the items of the menu accessories as
well. (i have a number of documents typeset in TeX.)

best regards
g. szeidl

(Continue reading)

headers

Evan Cooch | 11 May 14:57

Re: winedt 5.6 -- what i miss

I see this sort of post a lot - not just for WinEdt, but software 
generally - makes me wonder (i) if WinEdt 5.5 did/does what you need, 
then why upgrade (I'm working on a couple of books, in a similar fashion 
to what you describe, and stayed with 5.5), and (ii) why didn't you 
simply install 5.6 into a separate directory, copy over whatever config 
files you needed, and work with it there to see if it did what you needed?

I think 'upgrade' has become almost reflexive, to the point where people 
stop thinking about whether or not the upgrade is actually needed 
(applies to hardware also - the user who does little more then email and 
web-browsing ditching old hardware that was perfectly functional for the 
latest and greatest machine, which is completely unnecessary). If there 
is a compelling new feature (for me, it would be code folding - here is 
my vote x10000 for code folding in 5.7), or improved stability (how can 
you tell with anything under Vista?), then perhaps a good reason to 
upgrade. Otherwise...why not leave well enough alone?

Not meaning to pick on Gyorgy at all - merely the general cycle I see of 
(i) upgrade out of no obvious necessity, (ii) post 
complaints/queries/pleas for why the 'new and improved' version is not 
doing what you want, when (iii) the older version probably was.

Just grist for the mill...

Gyorgy SZEIDL wrote:
> dear alex and list members,
>
> winedt 5.6 has changed a lot. some of the changes are however
> negative ones.
>

(Continue reading)

headers

Ken Lloyd | 11 May 17:28

RE: winedt 5.6 -- what i miss

Being a software developer, I hold these conversations between users and the
developer close to my heart.

First, from Alex's point of view, he is trying his best to maintain a
successful application in light of changing technological contexts.  I found
that maintenance functions are often anathema to original engineered intent
and evolved usage. After three major revisions or in about 5 - 7 years, it's
about time to re-engineer the whole thing from the ground floor - it's
developed too much entropy to maintain.  I feel for Alex.

So Evan's right.  If software is working for you, keep using it until the
pain of continuing is equal to the pain of switching (see Vista vs. WinXP).
There is a steep cost for being at the cutting edge all the time, as
witnessed by the "blood" spilled on these pages. 

Of course, a certain percentage of the population are masochists ... Many of
them become software developers and writers of technical papers (or both).

Ken Lloyd

> -----Original Message-----
> From: Evan Cooch [mailto:evan.cooch <at> cornell.edu] 
> Sent: Sunday, May 11, 2008 6:57 AM
> To: winedt+list <at> wsg.net
> Subject: Re: [WinEdt] winedt 5.6 -- what i miss
> 
> I see this sort of post a lot - not just for WinEdt, but 
> software generally - makes me wonder (i) if WinEdt 5.5 
> did/does what you need, then why upgrade (I'm working on a 
> couple of books, in a similar fashion to what you describe,

(Continue reading)

headers

Hector C | 12 May 09:24

Re: winedt 5.6 -- what i miss

Gyorgy SZEIDL wrote:
> dear alex and list members,
> 
> (direct search or dvi search) ... this icon is not available 
> anymore in the main window. 
Doesn't Ctrl+Shift+S work for you?

> 2. i have no idea how to make a pdf file from a traditional TeX file.
I don't think there is a default keyboard shortcut for PDF Tex, but you 
can define your own: Options->Menu Setup->(this tab should be already 
selected)Main Menu->(double click on)&Accessories->(navigate in the Menu 
Items list down to)PDF Te&Xify->change the shortcut. If you don't want 
to define your own shortcut, you can always navigate the menus with the 
keyboard: "Alt+A, P, X" will do what you need.

Cheers,

Hector C

headers

Gyorgy SZEIDL | 12 May 11:47

what i miss -- ii. thank you for your kind responds

dear list members,

thank thank you for your responds.

I see this sort of post a lot - not just for WinEdt, but software generally -
makes me wonder (i) if WinEdt 5.5 did/does what you need, then why upgrade
(I'm working on a couple of books, in a similar fashion to what you describe, and
stayed with 5.5), and (ii) why didn't you simply install 5.6 into a separate directory,
copy over whatever config files you needed, and work with it there to see if it did
what you needed?

I think 'upgrade' has become almost reflexive, to the point where people stop thinking
about whether or not the upgrade is actually needed (applies to hardware also - the
user who does little more then email and web-browsing ditching old hardware that was
perfectly functional for the latest and greatest machine, which is completely unnecessary).
If there is a compelling new feature (for me, it would be code folding - here is my vote
x10000 for code folding in 5.7), or improved stability (how can you tell with anything under
Vista?), then perhaps a good reason to upgrade. Otherwise...why not leave well enough
alone?

your reasoning about the issue why one should upgrade seems to be right. as regards winedt however
each upgrade provided a more user friendly environment and this is the reason why i decided to upgrade
after winedt 5.6 beta 1 came out. (the good experiences have, of course, influence on one's decision). in
addition without knowing what new features an upgrade has you can not decide whether to upgrade
(or not). a description is simply not enough for me to make a decision.

Being a software developer, I hold these conversations between users and the developer close to my heart. First, from Alex's point of view, he is trying his best to maintain a successful application in light of changing technological contexts. I found that maintenance functions are often anathema to original engineered intent and evolved usage. After three major revisions or in about 5 - 7 years, it's about time to re-engineer the whole thing from the ground floor - it's developed too much entropy to maintain. I feel for Alex. So Evan's right. If software is working for you, keep using it until the pain of continuing is equal to the pain of switching (see Vista vs. WinXP). There is a steep cost for being at the cutting edge all the time, as witnessed by the "blood" spilled on these pages. Of course, a certain percentage of the population are masochists ... Many of them become software developers and writers of technical papers (or both). i have developed a number of programs in fortran 90 and i dare say that i know what developing a
en engineering program means.

i raised two issues.

the first one is really important. i work on two long projects and when making corrections i can do that
faster if the direct search is available from the main menu. and this conclusion is valid for anyone who is
writing a long document under latex.

as to the traditional TeX users their number seems to decrease since LaTeX becomes more popular.
in spite if that it is a natural requirement that they can create a pdf file from their documents.

I don't think there is a default keyboard shortcut for PDF Tex, but you can define your own: Options->Menu Setup->(this tab should be already selected)Main Menu->(double click on)&Accessories->(navigate in the Menu Items list down to)PDF Te&Xify->change the shortcut. If you don't want to define your own shortcut, you can always navigate the menus with the keyboard: "Alt+A, P, X" will do what you need.

thank you. i shall give it a try.

the key combinations that are used as commands are really useful.
in spite of that i get used to my mouse.

thank you for your kind responds once again.

with best regards
g. szeidl

Gyorgy SZEIDL wrote:
dear alex and list members,

(direct search or dvi search) ... this icon is not available anymore in the main window.
Doesn't Ctrl+Shift+S work for you?

2. i have no idea how to make a pdf file from a traditional TeX file.

I don't think there is a default keyboard shortcut for PDF Tex, but you can define your own: Options->Menu Setup->(this tab should be already selected)Main Menu->(double click on)&Accessories->(navigate in the Menu Items list down to)PDF Te&Xify->change the shortcut. If you don't want to define your own shortcut, you can always navigate the menus with the keyboard: "Alt+A, P, X" will do what you need.

Cheers,

Hector C

headers

WinEdt Team | 12 May 22:26

Re: what i miss -- ii. thank you for your kind responds

> i raised two issues.

Both are really "non-issues" and they can be easily addressed
on your side. They both translate to the following:

You want to put two buttons in the toolbar. This can be easily
done (as was the case in all versions of WinEdt).

> the first one is really important. i work on two long projects
> and when making corrections i can do that faster if the direct
> search is available from the main menu. and this conclusion is
> valid for anyone who is writing a long document under latex.

The menu item for forward search is already defined and it has
a button (and a shortcut) associated with it (check it in the
menu setup dialog).

Right-Click on the toolbar and chose Enter Toolbar Setup. Click
on this button (somewhere down the list) and then click on the
place in the toolbar where you want to move it (eg. after DVI
Preview). Help (Index -> Toolbar) explains the procedure in
detail... Problem 1. solved

> as to the traditional TeX users their number seems to decrease
> since LaTeX becomes more popular. in spite if that it is a
> natural requirement that they can create a pdf file from their
> documents.

Accessories menu (under PDF submenu) contains all PDF
generators (including plain PDF TeX). Want it in the toolbar?
Repeat the procedure above with this button. Problem 2.
solved

It should not take you more than a minute and now you know that
Menu and Toolbar are user-customizable...

Best regards,

alex

headers

Gyorgy SZEIDL | 13 May 09:37

what i miss -- iii. -- thank you for the solution

dear alex,

thank you for very much for your kind reply which clearly shows that my familiarity
with the possibilities offered by winedit is far from being sufficient (though i have
added a number of commands to the insert and document menus). i am convinced
however that the beginner as well as the average user do not bother to much about
these features. instead they use winedt as it is.

thank you once again. (i shall follow your advice which has resolved my problems)

with kind regards
g. szeidl

i raised two issues.

Both are really "non-issues" and they can be easily addressed
on your side. They both translate to the following:

You want to put two buttons in the toolbar. This can be easily
done (as was the case in all versions of WinEdt).

the first one is really important. i work on two long projects
and when making corrections i can do that faster if the direct
search is available from the main menu. and this conclusion is
valid for anyone who is writing a long document under latex.

The menu item for forward search is already defined and it has
a button (and a shortcut) associated with it (check it in the
menu setup dialog).

Right-Click on the toolbar and chose Enter Toolbar Setup. Click
on this button (somewhere down the list) and then click on the
place in the toolbar where you want to move it (eg. after DVI
Preview). Help (Index -> Toolbar) explains the procedure in
detail... Problem 1. solved

as to the traditional TeX users their number seems to decrease
since LaTeX becomes more popular. in spite if that it is a
natural requirement that they can create a pdf file from their
documents.

Accessories menu (under PDF submenu) contains all PDF
generators (including plain PDF TeX). Want it in the toolbar?
Repeat the procedure above with this button. Problem 2.
solved

It should not take you more than a minute and now you know that
Menu and Toolbar are user-customizable...

Best regards,

alex

--
Prof. Dr. habil György SZEIDL
Department of Mechanics
University of Miskolc
3515 Miskolc-Egyetemváros
Hungary
Phone: 36-46-565-111 ext. 18-92
URL: http://www.mech.uni-miskolc.hu/staff/lecturers/G_Szeidl.html

headers

Stratis Kounias | 13 May 11:28

Re: what i miss -- ii. thank you for your kind responds

Please delete my name from your list

Stratis Kounias
----- Original Message ----- 
From: "WinEdt Team" <support <at> winedt.com>
To: <winedt+list <at> wsg.net>
Sent: Monday, May 12, 2008 11:26 PM
Subject: Re: [WinEdt] what i miss -- ii. thank you for your kind responds

>> i raised two issues.
> 
> Both are really "non-issues" and they can be easily addressed
> on your side. They both translate to the following:
> 
> You want to put two buttons in the toolbar. This can be easily
> done (as was the case in all versions of WinEdt).
> 
>> the first one is really important. i work on two long projects
>> and when making corrections i can do that faster if the direct
>> search is available from the main menu. and this conclusion is
>> valid for anyone who is writing a long document under latex.
> 
> The menu item for forward search is already defined and it has
> a button (and a shortcut) associated with it (check it in the
> menu setup dialog).
> 
> Right-Click on the toolbar and chose Enter Toolbar Setup. Click
> on this button (somewhere down the list) and then click on the
> place in the toolbar where you want to move it (eg. after DVI
> Preview). Help (Index -> Toolbar) explains the procedure in
> detail... Problem 1. solved
> 
>> as to the traditional TeX users their number seems to decrease
>> since LaTeX becomes more popular. in spite if that it is a
>> natural requirement that they can create a pdf file from their
>> documents.
> 
> Accessories menu (under PDF submenu) contains all PDF
> generators (including plain PDF TeX). Want it in the toolbar?
> Repeat the procedure above with this button. Problem 2.
> solved
> 
> It should not take you more than a minute and now you know that
> Menu and Toolbar are user-customizable...
> 
> Best regards,
> 
> alex
> 
>

headers

Ferdinand Fichtner | 13 May 15:51

RE: ANN: WinEdt 5.6

Hi Alex:

One more thing related to the console I noticed:

If you start a console-task with a shortcut (say, Shift-Ctrl-X for Texify)
and the console is not ready to execute the task due to another application
still being active in the console (e.g. a task waiting for user input), the
last key pressed as part of the shortcut (the 'X' in the Texify example)
ends up in the current document as a character. This happens after the
Information Dialog ("Another Application is already running in WinEdt's
console...") is dismissed with 'Ok'.

I think you should consider correcting this. Otherwise, strange orphaned
characters might show up in Winedt users' documents...

Best regards!

Ferdinand

> -----Original Message-----
> From: WinEdt Team [mailto:support <at> winedt.com] 
> Sent: Wednesday, April 30, 2008 7:28 PM
> To: winedt+list <at> wsg.net
> Subject: [WinEdt] ANN: WinEdt 5.6
> 
> Beta version of WinEdt 5.6 is now available for testing.
> 
> Read the instructions carefully and proceed accordingly. You 
> should also read the What's New section for description of 
> all the changes, bug fixes, etc...
> 
> This version may not be for everyone: Macros in Exec folder 
> have been rewritten and the Accessories Menu for MiKTeX and 
> TeX Live has been changed to call the new (common) macros 
> that can execute console applications in WinEdt's Console. 
> Restoring the old macros in Exec folder or the old 
> Accessories Menu will not (can not!) work properly with the 
> new Execution Modes...
> 
> Documentation is yet to be updated: reading the What's New 
> file is the only way to get familiar with the new functionality.
> 
> Have fun.
> 
> Best regards,
> 
> alex

headers

WinEdt Team | 27 May 02:19

Re: ANN: WinEdt 5.6

Ferdinand,

> One more thing related to the console I noticed:
>
> If you start a console-task with a shortcut (say, Shift-Ctrl-X
> for Texify) and the console is not ready to execute the task
> due to another application still being active in the console
> (e.g. a task waiting for user input), the last key pressed as
> part of the shortcut (the 'X' in the Texify example) ends up in
> the current document as a character. This happens after the
> Information Dialog ("Another Application is already running in
> WinEdt's console...") is dismissed with 'Ok'.
>
> I think you should consider correcting this. Otherwise, strange
> orphaned characters might show up in Winedt users' documents...

yes, there were some message processing and focus switching
oddities with the way the console was implemented. This has now
been fixed by implementing custom code (event handlers and all)
that replaces RichEdit control currently used in the console.
The next version will provide a more "standard" and robust
console behavior.

Best regards,

alex