Richard Vaughn | 4 Feb 17:41 2011
Picon

Re: Viewing dvi output source in WinEdt (not notepad)

This is still not working.

Here's what happens.
User opens a TeX file w/ WinEdt.
He TeXify's the file, which works fine.
Then he DVI's the file, after which the DVI version is displayed.

However, when he double-clicks on a portion of the DVI version
so that he can modify the document, two not-good things happen.
A) The doc is displayed in Notepad, not WinEdt.
B) It does not open to the spot in the doc where he double-clicked.

Backstory:
Windows 7
WinEdt 6; Build 20101215 (v6.0)
MikTeX 2.8

File type .dvi is associated with WinEdt.

In Yap 2.8.3503: View > Options > Inverse DVI Search,
Command line is as follows:
"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]

Thoughts on this?

Thanks!
-Richard Vaughn 


On 1/19/2011 2:57 PM, Jeff E. Lewis wrote:
Don't know what version of WinEdt or MiKTeX ---

In YaP (2.9)

View -> Options -> Inverse DVI Search

and follow the steps to put in

c:<WinEdt Directory>\winedt.exe "[Open('%f');SelLine(%l,7)]"

Best regards,
Jeff E. Lewis
At 12:57 PM 1/19/2011, you wrote:
One of my users (a Physics professor) has a WinEdt issue.

When he doubleclicks on dvi output, it opens the source
code in Notepad rather than in Winedt.   This is important,
since he does a lot of work on tex files.

Mustn't there be a setting somewhere to point to Winedt instead of notepad?
How is this remedied?

Thanks,
-Richard Vaughn

Prof. Jeff E. Lewis
Professor of Mathematics, Emeritus
Honors College Associate Dean for Academic Affairs, Emeritus
Tel: Office: +1-312-413-9586, Home (preferred): +1-312-421-4394, TrustFax: +1-866-571-9921
e-mail: jlewis <at> uic.edu
http://www.math.uic.edu/~lewis/


-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
Karl Koeller | 4 Feb 17:51 2011

Re: Viewing dvi output source in WinEdt (not notepad)

Il 04/02/2011 17.41, Richard Vaughn ha scritto:
This is still not working.

Here's what happens.
User opens a TeX file w/ WinEdt.
He TeXify's the file, which works fine.
Then he DVI's the file, after which the DVI version is displayed.

However, when he double-clicks on a portion of the DVI version
so that he can modify the document, two not-good things happen.
A) The doc is displayed in Notepad, not WinEdt.
B) It does not open to the spot in the doc where he double-clicked.

Backstory:
Windows 7
WinEdt 6; Build 20101215 (v6.0)
MikTeX 2.8

File type .dvi is associated with WinEdt.

In Yap 2.8.3503: View > Options > Inverse DVI Search,
Command line is as follows:
"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]

Thoughts on this?

Thanks!
-Richard Vaughn 


On 1/19/2011 2:57 PM, Jeff E. Lewis wrote:
Don't know what version of WinEdt or MiKTeX ---

In YaP (2.9)

View -> Options -> Inverse DVI Search

and follow the steps to put in

c:<WinEdt Directory>\winedt.exe "[Open('%f');SelLine(%l,7)]"

Best regards,
Jeff E. Lewis
At 12:57 PM 1/19/2011, you wrote:
One of my users (a Physics professor) has a WinEdt issue.

When he doubleclicks on dvi output, it opens the source
code in Notepad rather than in Winedt.   This is important,
since he does a lot of work on tex files.

Mustn't there be a setting somewhere to point to Winedt instead of notepad?
How is this remedied?

Thanks,
-Richard Vaughn

Prof. Jeff E. Lewis
Professor of Mathematics, Emeritus
Honors College Associate Dean for Academic Affairs, Emeritus
Tel: Office: +1-312-413-9586, Home (preferred): +1-312-421-4394, TrustFax: +1-866-571-9921
e-mail: jlewis <at> uic.edu
http://www.math.uic.edu/~lewis/


-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
first of all, you have to associate .dvi files with yap, not with winedt!!!!!!!!!!!!!!!!
David Denton | 4 Feb 17:55 2011
Picon

PDF-XChange forward (and inverse) search

Hello,

I am using Build: 20110119 (v. 6.0).

I really like the yellow highlighting forward search with
PDF-Xchange, however sometimes when it can be annoying -- for
example when creating presentations with Beamer. Where in the
options can the highlighting feature be turned off?

A related question: Where are you, Alex, in discussions with
Tracker concerning the inverse search? Is this something that
will happen in a coming version?

--

-- 
Best regards,
 David

Richard Vaughn | 4 Feb 19:50 2011
Picon

Re: Viewing dvi output source in WinEdt (not notepad)

Correction re this:

The user does not want to edit a .dvi  file. He wants to edit the .tex  file.
Clicking on the dvi output should take him back to the relevant .tex code,
but it doesn't, which is the problem.

-Richard

On 2/4/2011 11:51 AM, Karl Koeller wrote:
Il 04/02/2011 17.41, Richard Vaughn ha scritto:
This is still not working.

Here's what happens.
User opens a TeX file w/ WinEdt.
He TeXify's the file, which works fine.
Then he DVI's the file, after which the DVI version is displayed.

However, when he double-clicks on a portion of the DVI version
so that he can modify the document, two not-good things happen.
A) The doc is displayed in Notepad, not WinEdt.
B) It does not open to the spot in the doc where he double-clicked.

Backstory:
Windows 7
WinEdt 6; Build 20101215 (v6.0)
MikTeX 2.8

File type .dvi is associated with WinEdt.

In Yap 2.8.3503: View > Options > Inverse DVI Search,
Command line is as follows:
"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]

Thoughts on this?

Thanks!
-Richard Vaughn 


On 1/19/2011 2:57 PM, Jeff E. Lewis wrote:
Don't know what version of WinEdt or MiKTeX ---

In YaP (2.9)

View -> Options -> Inverse DVI Search

and follow the steps to put in

c:<WinEdt Directory>\winedt.exe "[Open('%f');SelLine(%l,7)]"

Best regards,
Jeff E. Lewis
At 12:57 PM 1/19/2011, you wrote:
One of my users (a Physics professor) has a WinEdt issue.

When he doubleclicks on dvi output, it opens the source
code in Notepad rather than in Winedt.   This is important,
since he does a lot of work on tex files.

Mustn't there be a setting somewhere to point to Winedt instead of notepad?
How is this remedied?

Thanks,
-Richard Vaughn

Prof. Jeff E. Lewis
Professor of Mathematics, Emeritus
Honors College Associate Dean for Academic Affairs, Emeritus
Tel: Office: +1-312-413-9586, Home (preferred): +1-312-421-4394, TrustFax: +1-866-571-9921
e-mail: jlewis <at> uic.edu
http://www.math.uic.edu/~lewis/


-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
first of all, you have to associate .dvi files with yap, not with winedt!!!!!!!!!!!!!!!!

-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
Karl Koeller | 4 Feb 20:37 2011

Re: Viewing dvi output source in WinEdt (not notepad)


>
> The user does not want to edit a .dvi  file. He wants to edit the
> .tex  file.
> Clicking on the dvi output should take him back to the relevant .tex code,
> but it doesn't, which is the problem.
>

I understood that.

> File type .dvi is associated with WinEdt.

But this one means your user understands nothing!

A hundred times in this list has been said that THIS IS NOT a winedt 
issue. It is a YAP issue...................

Do you understand this?

> In Yap 2.8.3503: View > Options > Inverse DVI Search,
> Command line is as follows:
> "C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
> "[Open(|%f|);SelPar(%l,8)]

I think you're missing a double quote at the end. It should be

"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe" 
"[Open(|%f|);SelPar(%l,8)]"

Itzhak Barkana | 4 Feb 22:26 2011
Picon

Re: Viewing dvi output source in WinEdt (not notepad)

OK, Karl, take it easy. It is probably just a typo, yet when "it doesn't work" one usually thinks of who knows what.

Anyway, to make sure, when one goes to...
 
In Yap 2.8.3503: View > Options > Inverse DVI Search,
...one  may first see that the program list is empty (or may have some other Editor than WinEdt.exe), so one must choose New, add the WinEdt.exe and only then the procedure will ask for the Command, that is right the way you wrote it .
 
In any case, it helped me too, so...
 
Many thanks,
Itzhak Barkana

From: Karl Koeller <karlkoeller <at> googlemail.com>
To: winedt+list <at> wsg.net
Sent: Fri, February 4, 2011 9:37:50 PM
Subject: Re: [WinEdt] Viewing dvi output source in WinEdt (not notepad)


>
> The user does not want to edit a .dvi  file. He wants to edit the
> .tex  file.
> Clicking on the dvi output should take him back to the relevant .tex code,
> but it doesn't, which is the problem.
>

I understood that.

> File type .dvi is associated with WinEdt.

But this one means your user understands nothing!

A hundred times in this list has been said that THIS IS NOT a winedt
issue. It is a YAP issue...................

Do you understand this?

> In Yap 2.8.3503: View > Options > Inverse DVI Search,
> Command line is as follows:
> "C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
> "[Open(|%f|);SelPar(%l,8)]

I think you're missing a double quote at the end. It should be

"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
"[Open(|%f|);SelPar(%l,8)]"
Richard Vaughn | 7 Feb 13:24 2011
Picon

Re: Viewing dvi output source in WinEdt (not notepad)

Itzhak:

Thanks for that.  Well said.
I've been on the WinEdt mail list for maybe 3 weeks now,
and out of nowhere this guy Koeller's giving me the third-degree over nothing.
I'm wondering 'What kind of neighborhood did I just walk into?'
Again, thanks.

-Richard Vaughn


On 2/4/2011 4:26 PM, Itzhak Barkana wrote:
<!-- DIV {margin:0px;} -->
OK, Karl, take it easy. It is probably just a typo, yet when "it doesn't work" one usually thinks of who knows what.

Anyway, to make sure, when one goes to...
 
In Yap 2.8.3503: View > Options > Inverse DVI Search,
...one  may first see that the program list is empty (or may have some other Editor than WinEdt.exe), so one must choose New, add the WinEdt.exe and only then the procedure will ask for the Command, that is right the way you wrote it .
 
In any case, it helped me too, so...
 
Many thanks,
Itzhak Barkana

From: Karl Koeller <karlkoeller <at> googlemail.com>
To: winedt+list <at> wsg.net
Sent: Fri, February 4, 2011 9:37:50 PM
Subject: Re: [WinEdt] Viewing dvi output source in WinEdt (not notepad)


>
> The user does not want to edit a .dvi  file. He wants to edit the
> .tex  file.
> Clicking on the dvi output should take him back to the relevant .tex code,
> but it doesn't, which is the problem.
>

I understood that.

> File type .dvi is associated with WinEdt.

But this one means your user understands nothing!

A hundred times in this list has been said that THIS IS NOT a winedt
issue. It is a YAP issue...................

Do you understand this?

> In Yap 2.8.3503: View > Options > Inverse DVI Search,
> Command line is as follows:
> "C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
> "[Open(|%f|);SelPar(%l,8)]

I think you're missing a double quote at the end. It should be

"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
"[Open(|%f|);SelPar(%l,8)]"

-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
Itzhak Barkana | 7 Feb 14:27 2011
Picon

Re: Viewing dvi output source in WinEdt (not notepad)

OK, OK, I thanked for the trigger that was probably needed as it finally helped, so let us give the un-needed part the benefit of doubt and treat it as just another (though longer) typo.
Itzhak

From: Richard Vaughn <rvaughn <at> physics.rutgers.edu>
To: winedt+list <at> wsg.net
Sent: Mon, February 7, 2011 2:24:39 PM
Subject: Re: [WinEdt] Viewing dvi output source in WinEdt (not notepad)

Itzhak:

Thanks for that.  Well said.
I've been on the WinEdt mail list for maybe 3 weeks now,
and out of nowhere this guy Koeller's giving me the third-degree over nothing.
I'm wondering 'What kind of neighborhood did I just walk into?'
Again, thanks.

-Richard Vaughn


On 2/4/2011 4:26 PM, Itzhak Barkana wrote:
OK, Karl, take it easy. It is probably just a typo, yet when "it doesn't work" one usually thinks of who knows what.

Anyway, to make sure, when one goes to...
 
In Yap 2.8.3503: View > Options > Inverse DVI Search,
...one  may first see that the program list is empty (or may have some other Editor than WinEdt.exe), so one must choose New, add the WinEdt.exe and only then the procedure will ask for the Command, that is right the way you wrote it .
 
In any case, it helped me too, so...
 
Many thanks,
Itzhak Barkana

From: Karl Koeller <karlkoeller <at> googlemail.com>
To: winedt+list <at> wsg.net
Sent: Fri, February 4, 2011 9:37:50 PM
Subject: Re: [WinEdt] Viewing dvi output source in WinEdt (not notepad)


>
> The user does not want to edit a .dvi  file. He wants to edit the
> .tex  file.
> Clicking on the dvi output should take him back to the relevant .tex code,
> but it doesn't, which is the problem.
>

I understood that.

> File type .dvi is associated with WinEdt.

But this one means your user understands nothing!

A hundred times in this list has been said that THIS IS NOT a winedt
issue. It is a YAP issue...................

Do you understand this?

> In Yap 2.8.3503: View > Options > Inverse DVI Search,
> Command line is as follows:
> "C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
> "[Open(|%f|);SelPar(%l,8)]

I think you're missing a double quote at the end. It should be

"C:\Program Files (x86)\WinEdt Team\WinEdt 6\winedt.exe"
"[Open(|%f|);SelPar(%l,8)]"

-- Richard Vaughn System Administrator Department of Physics and Astronomy Rutgers University 126 Frelinghuysen Rd. / E374 Piscataway, NJ 08854 732.445.5500, x2845
Henning Haida | 7 Feb 15:06 2011
Picon

Command prompt opened from WinEdt -- Win XP vs. Win 7

Hi,

recently I realized a problem invoking gnuplot from (pdf)latex. Although
--enable-write18 is set (shell escape with MiKTeX) the gnuplot call was
not successful on Windows 7. Investigating this, I found a difference in
the command prompt opened from WinEdt on on the one hand Windows XP and
on the other hand Windows 7.

- Win XP/WinEdt 6/MikTeX 2.9: Opening a command prompt via the button in
WinEdt. Typing gnuplot there opens the gnuplot program (as expected).

- Win 7/WinEdt 6/MiKTeX 2.9: Opening a command prompt via the button in
WinEdt; typing gnuplot: The program could not be found.

On both machines, XP and Win 7, gnuplot opens fine via typing gnuplot in
cmd.exe.

Is this an Windows 7 issue? Or a configuration of WinEdt?

Any help is appreciated, kindest regards
 Henning

PS: I'd like to thank the list admin for his assistance!

Stefan Pinnow | 7 Feb 15:46 2011
Picon
Picon

RE: Command prompt opened from WinEdt -- Win XP vs. Win 7

Hello Henning,

> recently I realized a problem invoking gnuplot from (pdf)latex. Although
> --enable-write18 is set (shell escape with MiKTeX) the gnuplot call was
> not successful on Windows 7. Investigating this, I found a difference in
> the command prompt opened from WinEdt on on the one hand Windows XP and
> on the other hand Windows 7.
> 
> - Win XP/WinEdt 6/MikTeX 2.9: Opening a command prompt via the button
> in WinEdt. Typing gnuplot there opens the gnuplot program (as expected).
> 
> - Win 7/WinEdt 6/MiKTeX 2.9: Opening a command prompt via the button
> in WinEdt; typing gnuplot: The program could not be found.
> 
> On both machines, XP and Win 7, gnuplot opens fine via typing gnuplot
> in cmd.exe.
> 
> Is this an Windows 7 issue? Or a configuration of WinEdt?

That sounds strange when gnuplot\binary really is in your Windows PATH.

I just add the path to the gnuplot binary directory to the WinEdt path under
	Options > Execution Modes > PATH > Extra PATH Folders
so it looks like
	%B;C:\Program Files (x86)\LaTeX\gnuplot\binary
because I don't need gnuplot elsewhere.

Best regards,
Stefan


Gmane