Mailing List Guidelines

     WinEdt Mailing List Guidelines
     ==============================

  These guidelines are sent to the WinEdt Mailing List once a month.
  Please keep them in mind when posting to the list.

  ---------------------------------------------------------------------

* What To Post

  The WinEdt Mailing List is for questions about the WinEdt editor. You
  should  not post questions concerning LaTeX, MiKTeX, BibTeX et al. to
  the mailing list. WinEdt is a shell/editor for  LaTeX  etc.  and  the
  list  is  intended  to  answer questions concerning WinEdt, not LaTeX
  etc. 
  (Sometimes it might be difficult  to  decide  whether  a  problem  is
  related to WinEdt or to MiKTeX, LaTeX etc. A rule of thumb is: If you
  are having the same  problems  when  running  the  program  from  the
  command line, it is NOT related to WinEdt.) 

  A lot of questions are being asked over and over  again.  Check  that
  your question isn't already answered in the WinEdt FAQ at 
     <http://www.winedt.org/Doc/FAQ> 
  or in the mailing list archives at 
     <http://groups.yahoo.com/group/WinEdt>.

  When sending a question to the mailing list, try to be specific. 
  Include (at least) 
    + the Build number of your WinEdt (see "Help | About WinEdt...")

Metropolitan Police of London is enquiring about Attempt to finance Terrorist Groups through India, Pakistan, Dubai, Kuwait, United Kingdom and United States of America

ANN: WinEdt 5 [Build 20050201 (v. 5.4)]

A new build has just been uploaded. Here are the News...

Best regards,

alex

WinEdt 5 [Build 20050201 (v. 5.4)] (working beta build)
=======================================================

- Installer now gives an option to create a Recovery folder with all
default WinEdt files. It uses about 10MB of hard drive space
(without affecting the size of the download) but it can come handy
if you manage to corrupt any of the configuration components or
files: defaults can be manually copied replacing the corrupted
ones... A few users in the past were asking about getting only
certain files for "repair" purpose: now they can have them.

- A bug with automatic matching of toggled delimiters has been
fixed: $\{0,1,2,\dots,T\}$

- The new Macro Call can now be used inside loops

- Delete and Backspace in softly indented documents now do what one
would expect

- Robert's LaTeX Doc macro is now a part of the default settings for
MiKTeX and fpTeX: check it out in the Help Menu.

- EDT Mode has been updated with highlighting for recently added
macros.

- More documentation in the new Help and extended and revisited
Demo.tex (the LaTeX Sample in the Documents Menu).

- HTML Help sources for the new WinEdt Help are no longer included
in order to reduce the size of the download by a few MB. They will
be made available separately after the official release...

- Menu item for GSView has been modified so as to preview the
currently edited eps or ps file (when applicable).

- A few enhancements to the default settings and a few minor bug
fixes as communicated on the Mailing List

- (A rare) Access violation when rapidly closing lots of softly
wrapped maximized documents in a resized Window has been detected
and fixed.

- A problem (access violation) with using a mouse wheel in a tree
control with less than 3 items has been fixed.

- YandY Configuration (as it was) is now again included in the
defaults...

Re: ANN: WinEdt 5 [Build 20050201 (v. 5.4)]

WinEdt Team wrote:

>
> WinEdt 5 [Build 20050201 (v. 5.4)] (working beta build)
> =======================================================
>
>
> - The new Macro Call can now be used inside loops

I can confirm this 

But are not all macros supposed to be usable (=playable) via Macro 
Recorder? Because if it is so, we have another bug with the Call and JMP 
macros. It seem that they are not parsed correctly by the Player.

Kind Regards,
Georges

Y&Y config bug in build 20050201

In a cleanly-installed Build 20050201 of WinEdt 4, with user profile, if 
I select the Y & Y configuration, I get pop-up Warning window:

   Can't Open Macro File "C:\Documents and Settings\Administrator\
   Application Data\WinEdt\Exec\YandY TeX\ExeMode.edt"

   Exe('%b\Exec\YandY TeX\ExeMode.edt'); ^^^ //Current Execution Mode

The same thing happened with a clean install of the same build but 
without using a user profile.
--

-- 
Murray Eisenberg                     murray <at> math.umass.edu
Mathematics & Statistics Dept.
Lederle Graduate Research Tower      phone 413 549-1020 (H)
University of Massachusetts                413 545-2859 (W)
710 North Pleasant Street            fax   413 545-1801
Amherst, MA 01003-9305

Re: ps2pdf

José A. Facenda Aguirre a écrit :

>hi all,
>I want to use ps2pdf button on winedt using a4 paper. So, in the file
>ps2pdf.bat I have the line
>
>gswin32c -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sPAPERSIZE=a4paper -sOutputFil
>e=%1.pdf -c save pop -f %1.ps
>if errorlevel 1 goto err
>
>But the output file is 215.9 x 279.4 mm. How can I fix rthis problem?
>Thanks in advance for any help
>José A. Facenda
>
>
>
>  
>
I think you have to verify that your dvips options are set to -Ppdf and 
-tA4...

Goodluck

--

-- 
 _______________________________
|   Sébastien Nguyen            |	
|   Tél. : 01 69 85 81 30       |
|   e-mail : snguyen <at> limsi.fr   |
|_______________________________|

Re: Y&Y config bug in build 20050201

> In a cleanly-installed Build 20050201 of WinEdt 4, with user
> profile, if I select the Y & Y configuration, I get pop-up Warning
> window:
>
>    Can't Open Macro File "C:\Documents and Settings\Administrator\
>    Application Data\WinEdt\Exec\YandY TeX\ExeMode.edt"
>
>    Exe('%b\Exec\YandY TeX\ExeMode.edt'); ^^^ //Current Execution Mode
>
> The same thing happened with a clean install of the same build but
> without using a user profile. -

I forgot to tell the installer to copy this file.

The line:

 Source: "WinEdt\Exec\YandY TeX\ExeMode.edt";
 DestDir: "{app}\Exec\YandY TeX"; Flags: onlyifdoesntexist

is missing in the install script.

Select YandY Configuration, ignore the error, start Options ->
Execution Modes and press "Default". This will create the missing
file and the error will no longer occur...

The file will be there in the next build. Any other problems with
YandY config?

Best regards,

alex

Re: ANN: WinEdt 5 [Build 20050201 (v. 5.4)]

> > - The new Macro Call can now be used inside loops
>
> I can confirm this 

That's good.

> But are not all macros supposed to be usable (=playable) via Macro
> Recorder? Because if it is so, we have another bug with the Call and
> JMP macros. It seem that they are not parsed correctly by the
> Player.

No: Macro Recorder was designed to record and play only simple
macros with each line being executable by itself. A "recording" can
be edited and embedded in a "proper" macro script which can then be
executed with a full power of macro language. It was always like
this and even Loops extending over one line are not allowed in the
recorder. Recorder can play what it can record (it assumes that
there are no errors in the recording!) and once you start editing
the script (by adding loops or labels) you have to execute it from
outside of the recorder...

I see no need to change this. Recorder was designed for simple
repetitive tasks. It has little value for writing "real" macro
scripts while it can allow unexperienced users to perform some
simple repetitive task...

However, I see that macro writers could use a simple Test.edt script
that can be conveniently edited and executed via a shortcut. This
makes it possible to debug and test macro segments before they get
embedded into a larger macro script. I will add items:

  Edit Test Macro    [Alt+F9?]
  Execute Test Macro [F9?]

to the Macros Menu (Test macro=%b\Macros\Recorder\Test.edt).

What do you think?

Best regards,

alex

In Quotation Macro

No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.4 - Release Date: 2005-02-01

Re: In Quotation Macro

> I have noticed that the GUI additions «IntQuotation» that works well
> with the previous version does not works with this build (20050201).
> The macro refuses to execute.

Even worse, WinEdt will refuse to execute any more macros after that
(until you restart it)...

Line: 69 in Install_IntQuotation.edt
             "Stop;");

Replace "Stop;" with an empty string ""

This is and was a bug in the macro (Stop; can only be used in the
Loop Macro).

Older Builds of WinEdt tolerated the bug but while I was fixing a problem 
with
Calls inside loops (Georges!) I made WinEdt more sensitive to such
calls. This will be fixed for the next build (coming soon). In the
meantime, restart WinEdt and then remove Stop; from where it should
not be!

Best regards,

alex