Feature or bug in project save

I am using Build: 20070501 (v. 5.5) and I notice that
when I save a project the "remove main file" menu item
becomes grayed out. Why is that? I would expect that
it would still be possible to remove the main file
once the project was saved.

Thanks for creating such a great editor. 

--Ryan

       
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting 

Re: Feature or bug in project save

> I am using Build: 20070501 (v. 5.5) and I notice that when I
> save a project the "remove main file" menu item becomes grayed
> out. Why is that? I would expect that it would still be
> possible to remove the main file once the project was saved.

It's a bug. It only occurs if the "Persistent Main File" option
in the Project Manager dialog is disabled.

It has now been fixed for the next build (coming soon)...

Best regards,

alex

Getting registers to work

I don't know if i'm extra dum this week or whatever it
might be but i can't get the following, seemingly easy
setup to work.

On my menu bar i have placed a command Blopp and it's
supposed to call the following macro:

Exe('%b\Exec\Acrobat CloseDoc.edt');
Run('compile.bat "test03"','%p');

I just realized that "test03" is not very general so i
went off to the Help and checked for the registers.
The on i got was %f - the current file. The problem
is that LaTeX seems to complain about file not being
found, so i'm guessing %f is not the key here.

What is? As in - how do i specify that i want the
current file to be compile.bat'ed?

Vänligen
Konrad
---------------------------------------------------

Sleep - thing used by ineffective people
            as a substitute for coffee

Ambition - a poor excuse for not having
                 enough sence to be lazy
--------------------------------------------------- 

Re: Getting registers to work

Hi Konrad,
try it without the "" and %N
I use
Run('make-all.bat %N');
I remember having the problem that the double quotes prevented the .bat 
file from finding the file. The first lines in my .bat are
set file=%1
pdflatex %file%
which works for me.

Greetings
Lars

Konrad Viltersten wrote:
> On my menu bar i have placed a command Blopp and it's
> supposed to call the following macro:
>
> Exe('%b\Exec\Acrobat CloseDoc.edt');
> Run('compile.bat "test03"','%p');
>
> I just realized that "test03" is not very general so i
> went off to the Help and checked for the registers.
> The on i got was %f - the current file. The problem
> is that LaTeX seems to complain about file not being
> found, so i'm guessing %f is not the key here.
>

Re: Getting registers to work

Lars Kaczmirek wrote/skrev/kaita/popisal/schrieb :

> Hi Konrad,
> try it without the "" and %N
> I use
> Run('make-all.bat %N');
> I remember having the problem that the double quotes prevented the
> .bat file from finding the file. The first lines in my .bat are
> set file=%1
> pdflatex %file%
> which works for me.
>
> Greetings
> Lars

Yes, it solved the problem. Thanks!

Vänligen
Konrad
---------------------------------------------------

Sleep - thing used by ineffective people
            as a substitute for coffee

Ambition - a poor excuse for not having
                 enough sence to be lazy
--------------------------------------------------- 

Adobe Reader 8...

Sorry if someoone has asked this recently, but I upgraded to Adobe Reader 
8.1 and the pdflatex macro button no longer works properly: it does not 
successfully clost the pdf file  before running pdflatex, causing pdflatex 
to hang because the pdf file is in use by another program.  I think a 
similar problem happened last time Adobe updated its reader.  What's the 
solution?

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

Chris Bourke
cbourke <at> cse.unl.edu
http://www.cse.unl.edu/~cbourke

Re: Adobe Reader 8...

Go back to Acrobat 7.

Actually, if you search the list, you'll find this issue has been talked to death, with various fixes and the like proposed. Many of these fixes are now coded into the latest and greatest build of WinEdt, so make sure you're using the latest version before pursuing further remedies.

Chris Bourke wrote:

Sorry if someoone has asked this recently, but I upgraded to Adobe Reader 8.1 and the pdflatex macro button no longer works properly: it does not successfully clost the pdf file  before running pdflatex, causing pdflatex to hang because the pdf file is in use by another program.  I think a similar problem happened last time Adobe updated its reader.  What's the solution?


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

Chris Bourke
cbourke <at> cse.unl.edu
http://www.cse.unl.edu/~cbourke

Pathname

Hi!

I like to use a main.tex file in the root directory of the current 
project, and several content files in subdirectories, e.g. 
"content/introduction.tex".
TeXLive 2007 codes the source specials as "content/introduction.tex".

My current dviout call is:
Run('c:\programme\dviout\dviout.exe -1 "%P\%N.dvi" # %!l "%n.tex"','%P')

which, however, does not add the "content/" to "introduction.tex", which 
is required by dviout to point to the current line.
Is there any global register that points to the relative path of the tex 
file?
Or is there another method (than hardcoding) to configure WinEdt to add 
the subdirectory folder "content/" + "%n.tex"?

Regards,
 Sebastian

Out of memory crash loading 1.56 GB in WinEdt 5.5

Hi,

I run WinEdt 5.5 on a Windows XP Professional x64 Edition - 4 GB
machine.

Loading a 1.56 GB tab seperated text file, 
WinEdt produces a series of out of memory error dialogs
and than crashes. A "send error report to Microsoft"
Dialog appears. Task Manager shows that WinEdt goes close 
to the 2 GB per process limit before crashing.

I would rather expect WinEdt to simply tell me that
my file is to big to be opend in a 32 bit process.

A bug in WinEdt ?

Best regards,

Nicki

--
Nicki Helfrich, Industrial Engineer / Economist
Fraunhofer Institute for Systems and Innovation Research
Sustainability and Infrastructures
Breslauer Str. 48, 76139 Karlsruhe, Germany
Tel. +49 721 / 6809-364
nicki.helfrich <at> isi.fraunhofer.de

Re: Command Completion Wizard with 5.5

More information... I didn't see the pop-up window(s) because they were 
hidden.  Here's what's actually happening:

If I type something and then press Ctrl-y (or Ctrl-Shift-y, or Alt-y, or 
Alt-Shift-y), then:

1. I get a pop-up window titled "Complete" with message:

       Can't find the macro list for WinEdt!
       we will try to work without these commands...

    I press OK button there.

2. I get a 2nd pop-up window with the same thing, and again click OK.

3. Now I get a new pop-up window, again titled "Complete", with the 
check-box list of "Latex", "Math Symbols", "Tex".  If I check any of 
these, say "Latex", I get yet a new pop-up window saying now:

       Can't find the command list 'Latex.lst'
       we will try to work without these commands...

I click the Exit button and now this last of the pop-ups are gone. But 
nothing else has happened.

What's going wrong???

Could there be some conflict with 5.5?  Or is the documentation saying 
to install in %B.... wrong and it should be %b... ?  (Doubtful, since 
the macros for the Command Completion Wizard all seem to have %B 
hard-coded into them in paths.)

Murray Eisenberg wrote:
> I'm having trouble getting the Command Completion Wizard plugin working 
> with WinEdt 5.5.  I unzipped the downloaded archive to 
> %B\Plugins\Complete and executed Install.edt from there.
> 
> If I type, e.g., \ne and press Ctrl-y (or Ctrl-Shift-y, or Alt-y, or 
> Alt-Shift-y), I see...nothing!  No pop-up window as the docs say I 
> should see.
> 
> What might be wrong?

--

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