Bravo!  Just for that simplification alone, I'm willing to pay a (reasonable) new license fee.  Even as a long-time WinEdt user, if it's been a while since I had to change some aspect of the configuration, I never know whether to go to Preferences, Settings, Appearance, Menu Setup, etc. -- the the point that I dread having to fritter away time to find where I need to change what needs to be changed.

One caveat to what I said:  If Y&Y TeX is not supported in WinEdt 6, then the program will have very limited value to me.  (Unless and until somebody creates a viewer engine for Windows as fast as dviwindo, I'm wedded to Y&Y TeX for most of my work.)

WinEdt Team wrote:

I am working on [version 6]....

Significant changes have been made to WinEdt's interfaces. In
particular, the way it is configured and customized has been
completely changed. Preferences, Settings, Appearance, Menu
Setup, and Highlighting Dialogs have been dropped (eliminated)
in favor of a new (consistent) Options Interface. ...

... I was also able to fix some
design mistakes: the old configuration dialogs were a result of
adding new functionality and options over many years: as a
consequence of such evolution they were overcrowded and lacking
logical organization.

I'll add to Murray's praise and support - I'd have no problem in paying for
an upgrade and giving a hand with testing, documentation etc.

Cheers,  Phil



  --
  Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f

  Sponsor:
  Prenditi un break e gioca con Kit Kat, ogni giorno in palio viaggi a Cuba per
te e i tuoi amici oltre a iTunes Card.
* Prova subito
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9891&d=7-12

Bravo!  Just for that simplification alone, I'm willing to pay a
(reasonable) new license fee.  Even as a long-time WinEdt user, if it's
been a while since I had to change some aspect of the configuration, I
never know whether to go to Preferences, Settings, Appearance, Menu
Setup, etc. -- the the point that I dread having to fritter away time to
find where I need to change what needs to be changed.

One caveat to what I said:  If Y&Y TeX is not supported in WinEdt 6,
then the program will have very limited value to me.  (Unless and until
somebody creates a viewer engine for Windows as fast as dviwindo, I'm
wedded to Y&Y TeX for most of my work.)

WinEdt Team wrote:
>
> I am working on [version 6]....
>
> Significant changes have been made to WinEdt's interfaces. In
> particular, the way it is configured and customized has been
> completely changed. Preferences, Settings, Appearance, Menu
> Setup, and Highlighting Dialogs have been dropped (eliminated)
> in favor of a new (consistent) Options Interface. ...
>
> ... I was also able to fix some
> design mistakes: the old configuration dialogs were a result of
> adding new functionality and options over many years: as a
> consequence of such evolution they were overcrowded and lacking
> logical organization.

--
Murray Eisenberg                     murray@...
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

> Hi all. Does anyone know when the final release date of WinEdt
> 6 will be? I heard it is the end of this year. However, we are
> already in December 2009.

I am working on it: It will be released in the beginning of
March.

Test versions might be available before that (as early as mid
January) but they may not be completely documented and some
changes to default settings might be done for the official
release depending on feedback...

Significant changes have been made to WinEdt's interfaces. In
particular, the way it is configured and customized has been
completely changed. Preferences, Settings, Appearance, Menu
Setup, and Highlighting Dialogs have been dropped (eliminated)
in favor of a new (consistent) Options Interface. Programming
work on WinEdt 6 is pretty much finished but lots of stuff has
to be documented or else I will be swamped with questions and
support requests...

Not many users know this but I had a pretty solid version of
WinEdt 6 ready more than a year ago. However, a dilemma arose
whether to release it as the first step towards the new setup
or to bite a bullet and replace the above dialogs with more
manageable interface. This took a lot of work and involved many
decisions on how to reorganize all the options. Once a decision
was made I was able to get rid of tens of thousands of lines of
legacy code (compatibility when it comes to loading the
settings from previous versions). I was also able to fix some
design mistakes: the old configuration dialogs were a result of
adding new functionality and options over many years: as a
consequence of such evolution they were overcrowded and lacking
logical organization. New functionality and enhancement to
highlighting ability has been made (for example environments
can have their background in custom colors -- the whole block
regardless of the length of text). Also changing a
configuration no longer requires rewriting the menu and toolbar
-- it is handled much more efficiently and switching between
TeX Live and MiKTeX is a "snap". And there is more...

Too much of old code was dealing with Import/ Export
functionality which was not well conceived, anyway (extracting
and loading configuration components with almost 100 macros for
this purpose in semi-editable format was never a good idea).
Anyway, all this has now been dealt with and the code is much
cleaner as a result. This makes a prospect of migrating to a
new Delphi compiler and producing a proper Unicode/ UTF-8
version (for version 6.1) much more feasible and less of a
nightmare. I am still working on a Backup/ Restore macros that
will allow smooth upgrading of Versions 6.x from here on
(although some changes might still be necessary for Unicode
version).

But there are also consequences that some users might find a
strong enough deterrent not to migrate to WinEdt 6:

   - Old settings cannot be automatically imported in new
   version. WinEdt 6 will have to be installed parallel to the
   old version (both can be run simultaneously) and any
   customizations will have to be done manually (this may
   require some reading of documentation). Running both versions
   simultaneously will allow you to compare, explore the new
   version and decide which you like better (at your leisure).

   - Components on WinEdt.org that use Import/ Export macros
   will not automatically install in the new version. They will
   have to be revisited and updated for WinEdt 6 (they should
   take advantage of the new Configuration Filters instead of
   reloading the menus directly!). This may take some time and
   will require the community to get involved...

   - WinEdt 6 requires a new code and this will require paying
   an upgrade fee. Exceptions will be made for users that bought
   a license or an upgrade within a year. Also users that are
   willing to get involved with updating of macros on WinEdt.org
   or want to help with documentation or make a reasonable
   contribution will be issued a new code free of change upon
   request...

If WinEdt 6 is reasonably well received the unicode version
should be available by the end of next year. Also some major
new functionality (like folding) will be considered. If, on the
other hand, WinEdt 6 will be a "flop" I'll have to reconsider
my options: perhaps the days of custom written and supported
shareware applications like WinEdt are numbered. No hard
feelings, though; it's been an interesting 15 years and I have
no regrets...

Best regards,

alex

Hi all.  Does anyone know when the final release date of WinEdt 6 will be?  I
heard it is the end of this year.  However, we are already in December 2009.

Quoting Daniele Giorgio Degiorgi <degiorgi@...>:

> Hi,
>
>
>
> With my settings (almost default) when I use Drag and Drop to copy or move a
> selected block, at the end of the operation the block is deselected.
>
> Thus if I am copying the same text in several place I have to select it
> again.
>
> Obviously, putting the text in the clipboard could be an alternative, but
> then the previous content of the clipboard is deleted and this is sometime
> not desired.
>
>
>
> Is there an option to keep the block selected?
>
>
>
> If not, such an option could be added in a future version.
>
>
>
> Thanks,
>
>
>
> Daniel
>
>

There is a small software named 'Clipomatic' which lets save several
entries in the clipboard (1 by default). It's very easy to use. Here's
the address:

http://www.mlin.net/Clipomatic.shtml

Regards,
Bernard

Hello again,

Wednesday, November 25, 2009, 5:34:03 PM, you wrote:

> I doubt that the above does anything useful in V.2 of
> PDFXChange.

Quite right.

> As per my previous messages SendMessage no longer
> works. The following works for me:

> // PDF-XChange?
>    FindInString(`%$('AcroRead');`,'PDFXCview',1,2,1000,1);
>    IfOK(!"Relax;",!"JMP('not_pdf-xchange')");
>    Run('%$("AcroRead"); /close:discard "%P\%N.pdf"');
>    PopTagsandRegisters;
>    Exit;
> :not_pdf-xchange::

This does work for me. Thanks for your help, alex.

> Note that in my previous mail I forgot semicolon after the
> variable %$("AcroRead"). That's what WinEdt was trying to tell
> you:

--
Best regards,
  David

> So I made some changes in Acrobat CloseDoc.edt as follows:
>
> // PDF-XChange?
>   FindInString(`%$('AcroRead');`,'PDFXCview',1,2,1000,1);
>   IfOK(!"Relax;",!"JMP('not_pdf-xchange')");
>   LetRegNum(1,0);
> :next_pdf-xchange::
>   LetRegNum(1,%!1+1);>
>   IfNum(%!1,99,'>',!"JMP('closed_pdf-xchange')");>
>   SendMessage("%N - PDF Viewer",$0111,$E152);
>   IfOK(!"JMP('closed_pdf-xchange')",!"Relax;");
>   SendMessage("- PDF Viewer",$0111,$E151);
>   JMP('next_pdf-xchange');
> :closed_pdf-xchange::
>   PopTagsandRegisters;
>   Exit;
> :not_pdf-xchange::
>
> This now works, but gives me a LaTeX error:
>
> "I can't write on file `----.pdf' Please type another file name
> for output:
>
> I press Enter and it is okay and the file reloads.

I doubt that the above does anything useful in V.2 of
PDFXChange. As per my previous messages SendMessage no longer
works. The following works for me:

// PDF-XChange?
    FindInString(`%$('AcroRead');`,'PDFXCview',1,2,1000,1);
    IfOK(!"Relax;",!"JMP('not_pdf-xchange')");
    Run('%$("AcroRead"); /close:discard "%P\%N.pdf"');
    PopTagsandRegisters;
    Exit;
:not_pdf-xchange::

Note that in my previous mail I forgot semicolon after the
variable %$("AcroRead"). That's what WinEdt was trying to tell
you:

> I tried replacing the SendMessage, but I now get other errors:
>
> ";" Expected
> ("AcroRead") ^^^ /close:discard "%P\N.pdf"

Best regards,

alex

> Re: I am using WinEdt Build: 20071003 (v. 5.5) and running it
> under Windows Visa
>
> I am opening a text file in a directory on a server and when I
> go save as it always take me back to c drive which I don't
> want. I want it to take me to the directory where I opened the
> file. If I do the same operation on my c drive it takes me to
> the directory where I opened the file. Can someone help me
> please?

I cannot confirm this on my network. With default settings the
things work as documented in the Help (Keyword: Startup
Folders). I did not see any do difference between local and
network (UNC) drives.

This functionality can be customized (depending on what you
want). For example, in the menu setup you may want to set %p as
a Startup Folder for this command...

Best regards,

alex

alex and WinEdt users,

As per my last message, I cannot get:

Run('%$("AcroRead") /close:discard "%P\%N.pdf"');

to work. However, I did note that there has been a change in how
Tracker installs the viewer. It is now installed as:

c:\Program Files\Tracker Software\PDF Viewer\PDFXCview.exe

So I made some changes in Acrobat CloseDoc.edt as follows:

// PDF-XChange?
   FindInString(`%$('AcroRead');`,'PDFXCview',1,2,1000,1);
   IfOK(!"Relax;",!"JMP('not_pdf-xchange')");
   LetRegNum(1,0);
:next_pdf-xchange::
   LetRegNum(1,%!1+1);>
   IfNum(%!1,99,'>',!"JMP('closed_pdf-xchange')");>
   SendMessage("%N - PDF Viewer",$0111,$E152);
   IfOK(!"JMP('closed_pdf-xchange')",!"Relax;");
   SendMessage("- PDF Viewer",$0111,$E151);
   JMP('next_pdf-xchange');
:closed_pdf-xchange::
   PopTagsandRegisters;
   Exit;
:not_pdf-xchange::

This now works, but gives me a LaTeX error:

"I can't write on file `----.pdf'
Please type another file name for output:

I press Enter and it is okay and the file reloads.

Again, I would really appreciate help in cleaning this up, so I
do not have to muddle around, not knowing what I am doing.

Thanks!

--
Best regards,
  David

Hello alex,

Tuesday, November 24, 2009, 9:18:14 PM, you wrote:

> Instead of SendMessage (which no longer works with v2) you must
> replace it with:

>   // This works with version 2 of PDF-XChange (nice and clean!)
>   Run('%$("AcroRead") /close:discard "%P\%N.pdf"');

> Manual in PDFXChange describes command line options available
> in version 2 (/close is one of the new ones)...

Thanks for your response. I am afraid that a little knowledge is
not necessarily a good thing. I hope you can appreciate that none
of this is clear to a non programmer. Any further help (like the
clean code of the whole macro, if possible) would be appreciated.

Thanks!

I tried replacing the SendMessage, but I now get other errors:

";" Expected
("AcroRead") ^^^ /close:discard "%P\N.pdf"

and then:

Error parsing a string parameter...
Run("%$("AcroRead") /close:discard "%P\N.pdf" ^^^);

I am actually not sure what I am to replace. All occurrences of
SendMessage?

Does all of:
SendMessage("%N - PDF-XChange Viewer",$0111,$E152);

Get replaced by:
Run('%$("AcroRead") /close:discard "%P\%N.pdf"');

What about:
SendMessage("%N - PDF-XChange Viewer",$0111,$E151);

And what about:
SendMessage("%$('Acro-Title');", $0000, $0000);

--
Best regards,
  David

> Completely forgetting about this problem from just a few weeks
> ago, I just updated PDF-XChange Viewer again to version 2,
> Build 42.9. I am paying for my short memory, again, in that
> Acrobat CloseDoc.edt bugs again.
>
> I ask again, has anyone else had problems with the recent
> builds of PDF-XChange Viewer closing and reloading when
> compiling? More importantly, could someone provide assistance
> in fixing Acrobat CloseDoc.edt so that it works again?

Instead of SendMessage (which no longer works with v2) you must
replace it with:

   // This works with version 2 of PDF-XChange (nice and clean!)
   Run('%$("AcroRead") /close:discard "%P\%N.pdf"');

Manual in PDFXChange describes command line options available
in version 2 (/close is one of the new ones)...

Best regards,

alex

----- Original Message -----
From: "David Denton" <ddenton@...>
To: <winedt+list@...>
Sent: Tuesday, November 24, 2009 6:41 PM
Subject: [WinEdt] PDF-XChange Viewer CloseDoc problems (bis)


> Hello,
>
> BTW, the error message that I get is:
>
> Cannot Open DDE Link to:
> "C:\Program Files\Tracker Software\PDF Viewer\PDFCview.exe"
> Service: acroview
> Topic: control
>
> DDEOpen('%$("AcroRead")',"acroview","control");
>
> --
> Best regards,
> David
>
>

Hello,

BTW, the error message that I get is:

Cannot Open DDE Link to:
"C:\Program Files\Tracker Software\PDF Viewer\PDFCview.exe"
Service: acroview
Topic: control

DDEOpen('%$("AcroRead")',"acroview","control");

--
Best regards,
  David

Hello Winedt users,

On Nov. 2, 2009, I wrote:

> I have had a difficult time with reloading documents using
> PDF-XChange Viewer. It appeared that Acrobat CloseDoc.edt macro
> was no longer working. I replaced the files with those from
> www.winedt.org\temp  and that did not work. Finally, I dealt with
> the only other thing that had changed in my installation,
> the new version of PDF-XChange Viewer.
>
> I went back to v. 2.0 build 42.5 from build 42.7, and now it
> works again like a charm. Anyone else had problems with the
> current build (42.7).

Completely forgetting about this problem from just a few weeks
ago, I just updated PDF-XChange Viewer again to version 2, Build
42.9. I am paying for my short memory, again, in that Acrobat
CloseDoc.edt bugs again.

I ask again, has anyone else had problems with the recent builds
of PDF-XChange Viewer closing and reloading when compiling? More
importantly, could someone provide assistance in fixing Acrobat
CloseDoc.edt so that it works again?

Many thanks in advance!

--
Best regards,
  David

For U-Jean's useful Backup macro at windedt.org...

Often I must open a .tex file in WinEdt for which there is yet no
backups done by the macro.  (For example, I move the file from another
computer.  Or I finished with the file a long time ago and deleted the
associated backup folders, but now I have to open it in WinEdt, perhaps
to copy parts to a new file, etc.)

Each time I do that, I get a pop-up windows "Windows cannot find '[file
name[]'. Make sure you typed the name correctly and then try again. To
search for a file, click the Start button, and then click Search."

And then it requires moving focus to that pop-up window and clicking the
OK button to dismiss it.

Is there some way to avoid that (for me, at least) annoying and
unnecessary behavior?

--
Murray Eisenberg                     murray@...
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

> > Isn't this a rather good way to build up a lot of
> superfluous out-of-
> > date junk in your files?
> >
>
> Hmm... Do you actually suggest to rewrite all my papers every
> time anyone
> comes up with a new "package"? Or even to bother to learn all this
> superfluous new stuff when old one (like amstex and epsf) is
> good enough?
> Sounds like the microsoft way (upgrade no matter whether you
> need it or
> not).

No, not at all.  What is already written and done with can just as well stay
as it is.

However, the poster here is presumably at odds with a piece he's writing now
and has either copied over from previous work or quite simply his editors
are a little less accommodating than yours ;-)

So, it might just be a good time for him to do some pruning.

Cheers,  Phil



  --
  Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f

  Sponsor:
  Sei pronto per l'inverno? Scoprilo giocando al concorso Danone, ogni settimana
puoi vincere 1.000 Euro!
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid˜75&d -11

>
> Not everyone needs or even knows how to use delimited parameters.

However, the case we are facing is precisely one where one NEEDS delimited
parameters, as some smart "package" writer decided to change their order.

>
> Isn't this a rather good way to build up a lot of superfluous out-of-
> date
> junk in your files?
>

Hmm... Do you actually suggest to rewrite all my papers every time anyone
comes up with a new "package"? Or even to bother to learn all this
superfluous new stuff when old one (like amstex and epsf) is good enough?
Sounds like the microsoft way (upgrade no matter whether you need it or
not).

> If I were you, I would rather write something like this at
> the beginning of my document:
>
> \\def\\getpsfig#1.eps,#2\\\\{\\ includegrapics[#2]{#1}}
> \\def\\psfig#1{\\getpsfig#1\\\\}

I suppose what you really meant was (hopefully I've properly doubled all the
\\'s)

\\def\\getpsfig figure=#1.eps,#2\\\\{\\includegraphics[#2]{#1}}

> and wouldn't bother with search/replace. (Don't use

Isn't this a rather good way to build up a lot of superfluous out-of-date
junk in your files?

> \newcommand: it sucks and doesn't let you have delimited
> parameters!)

Not everyone needs or even knows how to use delimited parameters.
This is rather reckless and pointless advice: it's downright wrong for a
novice, who would risk running into precisely the clashes \\newcommand is
set up to avoid and an expert just doesn't need it.

> Actually, personally I always leave such things
> to the editors: if they don't like the styles/files that I'm
> using, it should be their problem.

You apparently only have to deal with very kind-hearted editors ... luck
you!

Cheers,  Phil



  --
  Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f

  Sponsor:
  Nuovo concorso Nestle' YOUWIN: vinci fantastici premi!
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid˜80&d -11

> I try it but I got
> Regular expression "psfig{figure=(1*).eps,width=(2*)}" not
> found in current document (forward)

Sorry, this is my e-mail provider - dunno why, but it apparently removes
unless it's escaped with another  !!!

So, here goes again:

Use search & replace with regular expressions and then insert
     \\psfig\{figure=\(\1*\).eps,width=\(\2*\)\}
as the search string and
     \\includegrapics\[width=\2\]\{\1\}
as the replace string
  --
  Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f

  Sponsor:
  Vinci subito fantastici premi, partecipando al gioco "alla faccia degli
amici" crea la faccia di chi vuoi tu e gioca!
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9867&d=20091120

I have a text like this
psfig{figure=fig14-1.eps,width=6.0 cm}
and i want to have it like this
includegrapics[width=6.0 cm]{fig14-1}
I have try to make a macro where I Repalace "psfig{figure=" with "includegrapics{
Then Replace ".eps," with "" and then Find "*m" which will find the "width=6.0 cm"
How can i copy the last Find and go back and put it in in the right position

Use search & replace with regular expressions and then insert
\psfig{figure=(1*).eps,width=(2*)}
as the search string and
\includegrapics[width=2]{1}
as the replace string
Cheers, Phil --
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f
Sponsor:
Vinci subito fantastici premi, partecipando al gioco "alla faccia degli
amici" crea la faccia di chi vuoi tu e gioca!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9867&d=20091120

> I have a text like this
>     psfig{figure=fig14-1.eps,width=6.0 cm}
> and i want to have it like this
>     includegrapics[width=6.0 cm]{fig14-1}
>
> I have try to make a macro where I Repalace  "psfig{figure="  with
> "includegrapics{
> Then Replace ".eps," with "" and then Find  "*m" which will find the
> "width=6.0 cm"
> How can i copy the last Find and go back and put it in in the
> right position

Use search & replace with regular expressions and then insert
     \psfig{figure=(1*).eps,width=(2*)}
as the search string and
     \includegrapics[width=2]{1}
as the replace string

Cheers,  Phil
  --
  Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f

  Sponsor:
  Vinci subito fantastici premi, partecipando al gioco "alla faccia degli
amici" crea la faccia di chi vuoi tu e gioca!
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9867&d=20091120

Hi
I have a text like this
     \psfig{figure=fig14-1.eps,width=6.0 cm}
and i want to have it like this
     \includegrapics[width=6.0 cm]{fig14-1}

I have try to make a macro where I Repalace  "\psfig{figure="  with
"\includegrapics{
Then Replace ".eps," with "" and then Find  "*\m" which will find the
"width=6.0 cm"
How can i copy the last Find and go back and put it in in the right position

Ola Ketil

am Freitag, 13. November 2009 um 01:28 schrieb Keshab Man Shrestha (Dr):


> Hello,
>         I recently installed Beamer with PDFlatex (Miktex) and when
> I compile from  winedit for the first time it creates
> a *.nav file and works fine. But when I recompile the same .tex
> file it gives me error. The only way for me to recompile is
> by deleting the *.nav file (the file with name same as the tex file
> with "nav" extension-I think it is supposed to be used
> by python or pearl).  I am trying to find out if there is a way to
> tell winedit to delete this file before compiling the
> tex file.

That's the wrong way to solve the problem. beamer is creating the
nav-file not for fun. It needs it later to get the navigation-menu
right. So try to find out what is wrong with your code or with beamer
by making a small example that demonstrates the problem.




--
Mit freundlichen Grüßen
Ulrike Fischer

Alex,
         Thanks for the advice. It works perfectly.

Best regards
Keshab

-----Original Message-----
From: WinEdt Team [mailto:support@...]
Sent: Saturday, November 14, 2009 2:01 AM
To: winedt+list@...
Subject: Re: [WinEdt] FW: problem with Beamer (latex) and .nav file

> I recently installed Beamer with PDFlatex (Miktex) and when I
> compile from winedit for the first time it creates a *.nav file
> and works fine. But when I recompile the same .tex file it
> gives me error. The only way for me to recompile is by deleting
> the *.nav file (the file with name same as the tex file with
> "nav" extension-I think it is supposed to be used by python or
> pearl). I am trying to find out if there is a way to tell
> winedit to delete this file before compiling the tex file.
> Otherwise, every time I need go recompile, I have to go to the
> folder and delete the .nav file.

WinEdt can automatically delete this file (although something
else is not quite OK if this keeps on happening). In WinEdt's
Exec\MiKTeX folder you will find a macro file PDFLaTeX.edt.

There you'll see a section like:

   // Delete the working output files...
   IfFileExists("%b\_Err.log",!"DeleteFile('%b\_Err.log')");
   IfFileExists("%b\_Out.log",!"DeleteFile('%b\_Out.log')");
   IfFileExists("%b\_Run.log",!"DeleteFile('%b\_Run.log')");
   IfFileExists("%P\%N.pdf",!"DeleteFile('%P\%N.pdf')");
   IfFileExists("%P\%N.log",!"DeleteFile('%P\%N.log')");

It's easy to see what you should do. Add a new line:

   IfFileExists("%P\%N.nav",!"DeleteFile('%P\%N.nav')");

That;s all.

Best regards,

alex


CONFIDENTIALITY: This email is intended solely for the person(s) named. The
contents may be confidential and/or privileged. If you are not the intended
recipient, please delete it, notify us, and do not copy or use it, nor disclose
its contents. Thank you.

Towards A Sustainable Earth: Print Only When Necessary