gmane.editors.winedt

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

Stratis Kounias — 2008-05-13T09:28:07

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

Winedt 5.6 error window

Daniele Giorgio Degiorgi — 2008-05-13T08:59:11

Hi, with 5.6 now an error windows opens at the bottom and I find it very good. I just noted a problem: double clicking the error (that contained a line number references) the cursor is set at that physical line, but if wrap is set the physical line does not correspond with the logical one. In my case, when an error is shown at line 19, then double clicking it result in the cursor (and highlighting) in line 12 as due to wrapping 7 previous lines were there. The same happen also at the end of Texify in case errors are encountered and some time I also saw that the wrong module was selected (possibly due to the same problem). Note that selecting line numbering correctly only numbers the start of a wrapped line and thus it is still easy to position to the right line. I just wonder if this is a small bug or if it can be changed with some appropriate setting. Thanks for any hint. Daniele

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

Gyorgy SZEIDL — 2008-05-13T07:37:20

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

Re: Saving text file in ASCII mode for the first time

Samuel Ieong — 2008-05-13T07:33:25

Hi Nicolas, Thank you very much for your reply. It looks I have the setting right, but it still doesn't quite exactly do what I thought it would do (the problem has to do with losing all line-spacing information). It's ok, just a minor annoyance .... I am more than happy otherwise. Thank you very much for replying. Regards, - Sam On Mon, May 12, 2008 at 5:32 PM, Nicolas Vaughan gmail.com> wrote:

RE: Re: Winedt 5.6/TexLive2007/dviout

Jonathan Ostroff — 2008-05-13T01:21:27

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

Re: Saving text file in ASCII mode for the first time

Nicolas Vaughan — 2008-05-13T00:32:38

Hi Sam, Try this: Go to Preferences > Defaults If "Trim Spaces (EOLN)" and "Trim Empty Lines (EOF)" are checked, remove the ASCII filter in the "Mode filter" for each one. Hope this helps, Regards, Nicolas Vaughan On Mon, May 12, 2008 at 7:09 PM, Samuel Ieong gmail.com> wrote:

Saving text file in ASCII mode for the first time

Samuel Ieong — 2008-05-13T00:09:30

Hi All, I am sorry this problem is probably easy to fix but I wasn't able to solve it after reading help and performing some experimentation. The problem has to do with saving a file in text mode for the first time, I ended up losing all spacing information. I felt that this must be related to the "keep all spaces" option under document properties, but even if that's checked, when I save the file, the problem persists. Is there something that I am missing? Version: 5.5 running on WinXP. Many thanks! Regards, - Sam

Re: Winedt 5.6/TexLive2007/dviout

Hector C — 2008-05-12T22:18:04

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);]\""

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

WinEdt Team — 2008-05-12T20:26:58

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 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:-) 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

Winedt 5.6/TexLive2007/dviout

Jonathan Ostroff — 2008-05-12T19:31:17

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

Winedt 5.6 console

=?iso-8859-15?Q?Agustin_E._Bolz=E1n?= — 2008-05-12T12:42:52

Dear Alex, I have found the new console very nice, especially because you can change from console to log file with a click. I wonder if it would also be included the gather window in this behaviour, i.e. one can open either the gather window from the console or open the console/log file window within the gather window. For the rest, it seems it runs very fine. Best regards, Agustin

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

Gyorgy SZEIDL — 2008-05-12T09:47:55

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

Re: winedt 5.6 -- what i miss

Hector C — 2008-05-12T07:24:58

Doesn't Ctrl+Shift+S work for you? 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

RE: winedt 5.6 -- what i miss

Ken Lloyd — 2008-05-11T15:28:22

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

Re: winedt 5.6 -- what i miss

Evan Cooch — 2008-05-11T12:57:12

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:

winedt 5.6 -- what i miss

Gyorgy SZEIDL — 2008-05-11T12:28:44

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

Re: WinEdt 5.6 -- texify does not work

Gyorgy SZEIDL — 2008-05-11T07:34:30

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

Re: bug in Vista

Evaristo Arroyo F. — 2008-05-11T02:31:19

En Sat, 10 May 2008 21:55:43 -0430, Evaristo Arroyo F. interlink.net.ve> escribió:

bug in Vista

Evaristo Arroyo F. — 2008-05-11T02:25:43

Re: Wrapping commented lines

WinEdt Team — 2008-05-10T21:07:21

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

Wrapping commented lines

Benatzky, Joachim — 2008-05-10T12:15:39

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.