Re: closing a project...

Strange. If you close only the main file manually then this operation
automatically 'unset' the main file.

Bernhard.

On 5/31/07, Chris Bourke <cbourke <at> cse.unl.edu> wrote:
>
>
> When I close a project, the "main file" does not become unset.  Is this
> intentional?  If so, what's the rationale?  How can I make it so that if a
> project is closed, the main file is "unset"?
>

RE: closing a project...

> When I close a project, the "main file" does not become 
> unset.  Is this 
> intentional?  If so, what's the rationale?  How can I make it 
> so that if a 
> project is closed, the main file is "unset"?

Very odd!  With my (latest) version of WinEdt the main file is definitely
unset on closing a project.

Cheers,  Phil

 

 --
 Email.it, the professional e-mail, gratis per te: http://www.email.it/f

 Sponsor:
 Donne e Motori! Gioie e Dolori?Noi pensiamo ai motori e alle gioie.
* Vieni a giocare
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6239&d=1-6

Re: closing a project...

> Strange. If you close only the main file manually then this
> operation automatically 'unset' the main file.

That depends on the option, Persistent Main File, in the Project
dialog.

> On 5/31/07, Chris Bourke <cbourke <at> cse.unl.edu> wrote:
> >
> >
> > When I close a project, the "main file" does not become unset.  Is this
> > intentional?  If so, what's the rationale?  How can I make it so that if 
> > a
> > project is closed, the main file is "unset"?

Cleanup upon closing a project is left to the event handler
(WinEdt\Macros\Events\Prj-Close.edt). By default it doesn't
remove anything but depending on how you want this
functionality to work you can change this in your
configuration:

  DeleteTree(1, $$0000);
  // DeleteTree(UseFlag: 0..1, Flag: $$0000..$$1111);
  //  UseFlag: 0..1
  //    0 delete the tree (as before)
  //    1 use flags to select the tasks
  //      Binary Flags from left to right $$0000..$$1111:
  //        Clear Gather Control
  //        Delete the Tree
  //        Clear File List
  //        Remove persistent Main File

Re: Re: new(?) approach to previewing MetaPost

>Speaking of which, I have some questions.
>
> 1. The metapost macro I wrote creates a tex file %n_proof.tex, and a
> list of existing files saved as %$('MP-filelist') .  Then it executes
> this line:
> WinExe('',`pdftex %n_proof.tex %$('MP-filelist')`,'%p','pdftex...',
> 01010100,0,'','','',110);
> which creates a pdf file containing the figures.
> Question: if I instead try to run this in detached mode, pdftex does
> not generate output.  Does this have something to do with the fact
> that this run of pdftex is taking %$('MP-filelist') as "arguments" to
> %n_proof.tex ?  I don't have a good understanding of what detached
> mode does at the Windows level.

For detached mode you must also specify redirected output and
error files. Most console applications don't work in detached
mode unless you redirect their output and error stream. As
always, there are exceptions, though...

I did not test this particular command but with properly
defined parameters I would expect it to work in detached mode
as long as pdftex.exe does not launch any additional
accessories (add .exe to the executable just in case). In
detached mode you should then be able to read the specified
error or output log file and see if there was indeed a problem.

 WinExe('',`pdftex.exe %n_proof.tex %$('MP-filelist')`,'%p','pdftex...',
 00001110,0,'','%b\Out.log','%b\Err.log',000);

> 2. When do variables need to end with a semicolon?  (In the example

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...")

Re: I have a problem

ANN: RSS, mpsproof, Toolkit Installator, ...

Greetings!

First a meta-announcement: WinEdt.org goes RSS!

If you always wanted to be the first to update packages but sometimes
missed to check the website every hour, if you are fed up of waiting for
the moment the webmaster sees himself fit (like today) to announce the
latest bunch of updates, or if you are simply overwhelmed by the traffic
on the list but don't want to miss any updates, then winedt.org's new
RSS news feed is for you:

  <http://www.winedt.org/rss.xml>

(What's RSS? : <http://www.rss-specifications.com/rss-faqs.htm> )

And now for something completely different:
_______________________________________________________________________

Jim Schummer has contributed his MetaPost macros, as communicated on the
list, to generate MP proof sheets and to display the current figure in
GSView.

  <http://www.winedt.org/Macros/LaTeX/MP-mpsproof.php>
_______________________________________________________________________

Erik Bartos has contributed the Installator Toolkit, a selection of
macros from www.winedt.org enriched with his own additions. The purpose
of the Toolkit Installator is the smooth installation of plugins, macros
and add-ons, without any need of manual adjustment.

  <http://www.winedt.org/Config/installator.php>
_______________________________________________________________________

The bibMacros package has been updated yet again: The "Find Entry" may
now be installed as the response to the "\cite..." Active Strings;
the dialog will display the bibliographies searched; this and the "Sort
Bibliography" macro can now really be used as stand-alone versions;
definitions for biblatex have been completed; some bugs have been caught.

  <http://www.winedt.org/Config/menus/BibTeX.php>
_______________________________________________________________________

The Mongolian dictionary by Bataka has been updated, now containing
700,000 words.

  <http://www.winedt.org/Dict/mn.txt>
_______________________________________________________________________

The DTX, EDTplus, and BibStyle modes have been updated for the latest
WinEdt build.

  <http://www.winedt.org/Config/modes/DTX.php>
  <http://www.winedt.org/Config/modes/EDTplus.php>
  <http://www.winedt.org/Config/modes/BibStyle.php>
_______________________________________________________________________

Finally, a surprise: Contributions are always welcome!

Happy WinEdt'ing!

For the winedt.org team,
  robert <at> winedt.org

Victor L Winter is out of the office.

I will be out of the office starting  06/05/2007 and will not return until
07/02/2007.

During this time I will have limited access to the internet.

Using WinEdt as a Stata editor

GhostScript AFPL and GPL

Hello:

It's the summer term and I have now time to take the plunge and update 
to Winedt 5.5 and MikTeX 2.5 (which is already considered obsolete).

Sourceforge lists two versions of GhostScript: AFPL Ghostscript 8.54 
(20060517) and GPL Ghostscript 8.57 (20070511). Is there any difference 
between the two variants AFPL and GPL? Any advice on which version to 
download and works well with Winedt+MikTeX? Thank you!

Tom