Strange Vista behavior

Re: Strange Vista behavior

> Last week I tried to install the Stata configuration on VISTA
> to no success because I couldn't access the install
> directories. But more seriously it appears that this broke my
> MikTeX configuration. Now when I open WinEdt I get a series of
> warnings like Path/button/new.bmp not found Path/images/new.bmp
> not found
>
> Then tree.ini and gather.ini do not execute because of files
> not found.
>
> I am writing to ask for advice on the best way to restore my
> MikTeX configuration.

It is possible that Stata configuration does not use
Application Data Folder and tries to copy files directly in
protected Program Files folder. On Vista this could cause
serious problems because of the way Windows handle such an
attempt.

Vista has a folder called VirtualStore (inside your
<User>\AppData\Local). Here it how it works: if application
tries to write in protected folder without administrative
privileges then a copy of data data is stored in this folder.
This can eventually become extremely confusing and dangerous as
most users may not know that and may erroneously assume that
they modified the original file and it may result in conflicts
as it is not clear which file is being loaded. I suggest that
you search for this folder and see if inside it there is WinEdt
Team folder. If yes, then delete WinEdt folder inside
VirtualStore\Program Files (it is not needed or wanted if you
have a user profile).

After that execute the Options -> Configurations -> MiKTeX to
restore MiKTeX Configuration. Actually you can try this first
to see if this will fix the problem. Otherwise cleaning up the
above folder will be required.

Best regards,

alex

RE: Strange Vista behavior

Thanks for the prompt response. I just fixed this problem by uninstalling and re-installing WinEdt and my
MikTeX installation seems to be back to full functionality. Now the problem is trying to install the Stata
configuration. In vista that path to the user application data is:

\Users\username\AppData\Roaming\WinEdt\Config\Stata for the Stata config files. I was able to get
WinZip to write the files there. But I can't get WinEdt to open a file from that folder. I got WinZip to write
there by typing the path in the dialog Window. WinZip didn't see the folder Vista was hiding. But WinEdt is
only letting me access folders that Vista thinks I should be able to see.

-----Original Message-----
From: WinEdt Team [mailto:support <at> winedt.com]
Sent: Monday, March 02, 2009 3:12 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Strange Vista behavior

> Last week I tried to install the Stata configuration on VISTA
> to no success because I couldn't access the install
> directories. But more seriously it appears that this broke my
> MikTeX configuration. Now when I open WinEdt I get a series of
> warnings like Path/button/new.bmp not found Path/images/new.bmp
> not found
>
> Then tree.ini and gather.ini do not execute because of files
> not found.
>
> I am writing to ask for advice on the best way to restore my
> MikTeX configuration.

It is possible that Stata configuration does not use
Application Data Folder and tries to copy files directly in
protected Program Files folder. On Vista this could cause
serious problems because of the way Windows handle such an
attempt.

Vista has a folder called VirtualStore (inside your
<User>\AppData\Local). Here it how it works: if application
tries to write in protected folder without administrative
privileges then a copy of data data is stored in this folder.
This can eventually become extremely confusing and dangerous as
most users may not know that and may erroneously assume that
they modified the original file and it may result in conflicts
as it is not clear which file is being loaded. I suggest that
you search for this folder and see if inside it there is WinEdt
Team folder. If yes, then delete WinEdt folder inside
VirtualStore\Program Files (it is not needed or wanted if you
have a user profile).

After that execute the Options -> Configurations -> MiKTeX to
restore MiKTeX Configuration. Actually you can try this first
to see if this will fix the problem. Otherwise cleaning up the
above folder will be required.

Best regards,

alex

RE: Strange Vista behavior

Sorry, I just fixed the problem. It was a matter of entering the full path in the first line of the open command
before using any of the icons to navigate.

-----Original Message-----
From: Nelson, Carl [mailto:chnelson <at> illinois.edu]
Sent: Monday, March 02, 2009 3:41 PM
To: winedt+list <at> wsg.net
Subject: RE: [WinEdt] Strange Vista behavior

Thanks for the prompt response. I just fixed this problem by uninstalling and re-installing WinEdt and my
MikTeX installation seems to be back to full functionality. Now the problem is trying to install the Stata
configuration. In vista that path to the user application data is:

\Users\username\AppData\Roaming\WinEdt\Config\Stata for the Stata config files. I was able to get
WinZip to write the files there. But I can't get WinEdt to open a file from that folder. I got WinZip to write
there by typing the path in the dialog Window. WinZip didn't see the folder Vista was hiding. But WinEdt is
only letting me access folders that Vista thinks I should be able to see.

-----Original Message-----
From: WinEdt Team [mailto:support <at> winedt.com]
Sent: Monday, March 02, 2009 3:12 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Strange Vista behavior

> Last week I tried to install the Stata configuration on VISTA
> to no success because I couldn't access the install
> directories. But more seriously it appears that this broke my
> MikTeX configuration. Now when I open WinEdt I get a series of
> warnings like Path/button/new.bmp not found Path/images/new.bmp
> not found
>
> Then tree.ini and gather.ini do not execute because of files
> not found.
>
> I am writing to ask for advice on the best way to restore my
> MikTeX configuration.

It is possible that Stata configuration does not use
Application Data Folder and tries to copy files directly in
protected Program Files folder. On Vista this could cause
serious problems because of the way Windows handle such an
attempt.

Vista has a folder called VirtualStore (inside your
<User>\AppData\Local). Here it how it works: if application
tries to write in protected folder without administrative
privileges then a copy of data data is stored in this folder.
This can eventually become extremely confusing and dangerous as
most users may not know that and may erroneously assume that
they modified the original file and it may result in conflicts
as it is not clear which file is being loaded. I suggest that
you search for this folder and see if inside it there is WinEdt
Team folder. If yes, then delete WinEdt folder inside
VirtualStore\Program Files (it is not needed or wanted if you
have a user profile).

After that execute the Options -> Configurations -> MiKTeX to
restore MiKTeX Configuration. Actually you can try this first
to see if this will fix the problem. Otherwise cleaning up the
above folder will be required.

Best regards,

alex

Converse of "Project/Set Main File" ? Suppress "PdfTeX failed to create a PDF file" ?

Using WinEDT  Build: 20040513  (v. 5.4)

Two queries :

1) Is it possible to perform the inverse of
"Project/Set Main File", by which I mean to mark a
given file (open in a tab) as a subsidiary project
file that should be auto-saved when any other file
(open in a tab) is processed ?

2) Is it possible to suppress the pop-up that occurs
when PdfTeX fails to create a PDF file ?  My first
two programs manipulate TeX data, and I do not wish
to generate a PDF file (which would then automatically
be displayed) because that would take focus away from
WinEDT.

To put both of these questions in context :

I have five tabs open : Sort-1.TeX, Sort-2.TeX,
Sort-3.Perl, Porphyrogenitus.TeX, and Byz-data.dat.
If I update Byz-data.dat, my next task will be
to process Sort-1.TeX (which will intentionally
produce no PDF output), then Sort-2.TeX (-- ditto --),
then to launch PERL on Sort-3.Perl, and finally
process Porphyrogenitus.TeX (which is the only
file that should produce a PDF).  Thus when I have
updated Byz-data.dat, I would like it auto-saved
when I launch Sort-1.TeX, without making Sort-1.TeX
the Project Main File (because if I were to do the
latter, I could not then process Sort-2.TeX, etc.).

Philip TAYLOR

Copying WinEDT (modified) to other systems

Using WinEDT Build: 20071003  (v. 5.5)

I finally gave up with the PERL module from
WinEDT.Org and decided to try to hack together
one of my own.  I used TtH as my starting point,
and cloned TtH.edt and TtH.bat to Perl.edt and
Perl.bat respectively, then edited each until
it appeared to do what I needed.  I then used
the Options / Menu Setup and Tool Bar Setup
to add a Perl macro and associate it with the
pre-supplied Camel button.  All now works as
I would wish, and I would now like to clone
this configuration to a number of different
machines, all of which co-operate in processing
the same sources and data.  What is the simplest
way of accomplishing this cloning operation, please ?

Philip TAYLOR

Re: Converse of "Project/Set Main File" ? Suppress "PdfTeX failed to create a PDF file" ?

> Using WinEDT Build: 20040513 (v. 5.4)
>
> Two queries :
>
> 1) Is it possible to perform the inverse of "Project/Set Main
> File", by which I mean to mark a given file (open in a tab) as
> a subsidiary project file that should be auto-saved when any
> other file (open in a tab) is processed ?
>
> 2) Is it possible to suppress the pop-up that occurs when
> PdfTeX fails to create a PDF file ? My first two programs
> manipulate TeX data, and I do not wish to generate a PDF file
> (which would then automatically be displayed) because that
> would take focus away from WinEDT.
>
> To put both of these questions in context :
>
> I have five tabs open : Sort-1.TeX, Sort-2.TeX, Sort-3.Perl,
> Porphyrogenitus.TeX, and Byz-data.dat. If I update
> Byz-data.dat, my next task will be to process Sort-1.TeX (which
> will intentionally produce no PDF output), then Sort-2.TeX (--
> ditto --), then to launch PERL on Sort-3.Perl, and finally
> process Porphyrogenitus.TeX (which is the only file that should
> produce a PDF). Thus when I have updated Byz-data.dat, I would
> like it auto-saved when I launch Sort-1.TeX, without making
> Sort-1.TeX the Project Main File (because if I were to do the
> latter, I could not then process Sort-2.TeX, etc.).

If you are asking can this be done: the answer is YES.

If you are asking are there a few options I can check and the
things will suddenly work as I want: the answer is NO.

You will have to customize the macros in WinEdt/Exec folder to
accomplish what you want. This part of WinEdt is open source and
it would be impossible to introduce hundreds of options for exotic
tasks as the one above.

If I was doing something like this I would probably write a
custom macro to compile the project. But that would take some
skill.

In Execution Modes you can disable the option to Wait for
Execution to finish and WinEdt will not display any warnings
(it also will not launch any previewer). This way you can work
manually in steps without a main file (it gives you more
control over each step). As for saving .dat file when you start
compilation on a current document: you can either add a command
to save all files in the macro or else manually save the file
after it is modified. Any further customizations will require
changes to macros that do the compilation...

Best regards,

alex

Sort command

Hi,

I recently discovered two problems using the sort command.

When sorting with enabled numeric digits then

A.2
A.10

Retains correctly the order while

A1.2
A1.10

Will be inverted.

It seems that a dot inside the numbers is treated different as other
characters.
This is possibly a good idea, but then giving the choice to treat dots like
non digits or use them in building real numbers could be a good extension.

There is another small problem (possibly a bug) when remove multiple entries
is selected: when k empty lines are in the selected area and the last line
of the selection is empty, then as result after the sort, the selected area
contains k-1 lines previously not selected.

Daniele

Section title does not appear in document

Re: Section title does not appear in document

Pedro A. Marrone a écrit :
> I have an strange problem. I am writing a book. I do have sections. But the
> section title does not appear in the document, but the section name does in
> the header. How can I get the section title to appear. The section title
> does appear in the table of Contents.
> 
>  
> 
> There is any way I can fix it, using the WinEdt Shell?
> 
> 

Aren't you typing :

\section[title]

and not

\section{title} ?

François