1 May 2012 12:41

### Forward search for PDF

Hello,

I'm having problems with forward search for PDF documents with Winedt 7.
PDF. With the latter, I get the error message "Unknown source file...".
If I compile to DVI and use Yap, forward search works fine.

I'm using Win7 64bit with MikTex 2.9.

Thanks & cheers,
Maarten


1 May 2012 14:07

### Re: Update for Figures&Tables contribution

Thanks for the new version.

I have investigated the gathering feature in the build 20120423 by
changing the necessary ? to TeX in Gather.ini . It only captures very
few figures unlike your macro that captures all of them. I will stick to

YC

On 4/30/2012 7:39 PM, Karl Koeller wrote:
> Starting with WinEdt 7 build 20120423, gathering of figure and table
> environments in TOC is included in the defaults. You only have to
> enable it (it can be done both in the Tree and in the Gather interfaces).
>
> The only difference between Figures&Tables package and the defaults is
> that in the first one figures and tables are collected as a separated
> branch in the Tree, while in the defaults they are collected as part
> of the TOC. The choice is yours.


1 May 2012 13:09

### Bug in WinEdt 7 Build 20140413 (re: TeXify shortcut key Ctrl-Alt-x)

Hi all

Has anyone else experienced this?

I’m compiling a document in WinEdt 7, and press Ctrl-Alt-X to run TeXify.

After pressing Ctrl-Alt-x and compilation finishes, a letter “x” is inserted where the cursor is located, i.e. the “x” is buffered and “placed” in the document when in fact it ought to have been a shortcut key.

Thanks

Hubert

1 May 2012 13:39

### Re: Update for Figures&Tables contribution

Il 01/05/2012 14.07, Yogeshwarsing Calleecharan ha scritto:
> Thanks for the new version.
>
> I have investigated the gathering feature in the build 20120423 by
> changing the necessary ? to TeX in Gather.ini . It only captures very
> few figures unlike your macro that captures all of them. I will stick
>
> YC

It is the same algorithm, so I don't know what you're talking about...

Maybe you want to collect them in the Tree, so you have to modify
Tree.ini and not Gather.ini...

Regards,

Karl


1 May 2012 13:40

### Re: Bug in WinEdt 7 Build 20140413 (re: TeXify shortcut key Ctrl-Alt-x)

Il 01/05/2012 13.09, Hubert Lam ha scritto:

Hi all

Has anyone else experienced this?

I’m compiling a document in WinEdt 7, and press Ctrl-Alt-X to run TeXify.

After pressing Ctrl-Alt-x and compilation finishes, a letter “x” is inserted where the cursor is located, i.e. the “x” is buffered and “placed” in the document when in fact it ought to have been a shortcut key.

Thanks

Hubert

This issue should have been solved in build 20120423...

Karl
1 May 2012 14:23

### RE: Bug in WinEdt 7 Build 20140413 (re: TeXify shortcut key Ctrl-Alt-x)

Thanks Karl. I’ll install and try again.

Hubert

From: Karl Koeller [mailto:karlkoeller <at> googlemail.com]
Sent: Tuesday, May 01, 2012 9:40 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Bug in WinEdt 7 Build 20140413 (re: TeXify shortcut key Ctrl-Alt-x)

Il 01/05/2012 13.09, Hubert Lam ha scritto:

Hi all

Has anyone else experienced this?

I’m compiling a document in WinEdt 7, and press Ctrl-Alt-X to run TeXify.

After pressing Ctrl-Alt-x and compilation finishes, a letter “x” is inserted where the cursor is located, i.e. the “x” is buffered and “placed” in the document when in fact it ought to have been a shortcut key.

Thanks

Hubert

This issue should have been solved in build 20120423...

Karl

1 May 2012 22:48

### Execution Modes grayed out

I have installed Winedt 7 on Windows 7 using standard options. I need
to change some settings in the Execution modes dialog box, but this
option is grayed out and I cannot open it. I am wondering what is
wrong with my settings.

Thanks,

Per


1 May 2012 23:01

### Re: Execution Modes grayed out

Il 01/05/2012 22.48, Per Ting ha scritto:
> I have installed Winedt 7 on Windows 7 using standard options. I need
> to change some settings in the Execution modes dialog box, but this
> option is grayed out and I cannot open it. I am wondering what is
> wrong with my settings.
>
> Thanks,
>
> Per
>

Did you installed over a previous build without following the upgrading
procedure?

Karl


1 May 2012 23:34

### Re: Forward search for PDF

Maarten,

This one will turn out to have nothing to do with WinEdt.

> I'm having problems with forward search for PDF documents with
> Pro or Sumatra PDF. With the latter, I get the error message
> "Unknown source file...". If I compile to DVI and use Yap, forward
> search works fine.
>
> I'm using Win7 64bit with MikTex 2.9.

For educational purposes:

You cannot compare dvi search with pdf search: the former one uses
SRC specials embedded by TeX in dvi file and the later one uses
supplementary sync information produced by TeX in .synctex file.

In the case of Adobe, WinEdt's own synctex parsing algorithm
cannot find any reference to the file from which you are
initiating the search in .synctex file. However, Sumatra PDF has
its own algorithm to parse synctex files and it, too, cannot
locate the source file from the available data in .synctex file.
So probably there is something wrong with it (remember it is
produced by TeX and not WinEdt).

Does the Inverse Search from Sumatra work?

Try:

0. Delete synctex file and recompile to generate a new one. Still
a problem?

1. Open one of WinEdt's LaTeX Samples (Documents Menu) and see if
it works with this one.

2. You can open your .synctex file in WinEdt (also check the date
on it) and then search for the name of the file from which you are
initiating the search. It should be somewhere there in semi-raw
text data. See if there is something odd there...

... and avoid spaces and international characters in filenames.
WinEdt has no problem with them but TeX often does.

That's just about all I can advise you (it is really not a WinEdt
issue)...

Best regards,

alex


1 May 2012 23:48

### RE: ANN: WinEdt 7 - minor bug

Hi again all,

Why was the Alt-Enter shortcut key removed? Would there be any possibility in restoring it (either in a
later build or by myself in some way?)

Whilst solutions have been offered, I'm still finding Alt-Enter to be easier :p

Thanks

Hubert
________________________________________
From: Karl Koeller [karlkoeller <at> googlemail.com]
Sent: Wednesday, 21 March 2012 7:14 AM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] ANN: WinEdt 7 - minor bug

Il 20/03/2012 21.08, Hubert Lam ha scritto:
> Hi Alex/all
>
> Just wondering if anyone else has installed WinEdt 7 but has lost the ability to press Alt-Enter to
"complete" the "\end{" statement?
>
> In WinEdt 5/6 I used to be able to type "\begin{enumerate}", hit Alt-Enter and it would autocomplete the
"\end{enumerate}" for me. The only thing that works now (which also worked before) is to type in
"\begin{enumerate}" and type in "\end{{" in order to have the autocomplete function.
>
> Having said that, it seems to be a far faster release -- WinEdt 6 could be quite slow in opening multiple
files (for a project).
>
> Thanks
>
> Hubert
> ________________________________________
> From: WinEdt Team [support <at> winedt.com]
> Sent: Wednesday, 21 March 2012 12:38 AM
> To: winedt+list <at> wsg.net
> Subject: Re: [WinEdt] ANN: WinEdt 7 - minor bug
>
>> I just installed WinEdt 7 on my Windows 7.
>>
>

Just type

\begin{enumerate}>



Gmane