EAGLE Central Forums
Where the EAGLE community meets. Sponsored by Stratford Digital.

Home » CadSoft Support Forums » eagle.support.eng » External text editor - again
External text editor - again [message #135839] Wed, 16 February 2011 15:26 Go to next message
Oppie[2]
Messages: 193
Registered: April 2009
Senior Member
Had a crash on my machine last week. All the important stuff was backed up
so just an annoyance... Lost a few configuration files.

Went to re-install Eagle 5.11 and set Notpad++ as my external editor. Was
making me absolutely crazy as I would enter the path and next time the
program opened, path was corrupted.

This is what finally worked (copied from eaglerc but entered from control
panel - Options - User interface). note that the eaglerc entry has an extra
set of quote marks bounding the entire string.
Interface.ExternalTextEditor = ""c:\Program Files\Notepad++\Notepad++.exe"
"%F""

Every time opened Eagle, the editor string was showing \ otepad++...

Finally realized that Case was **important**
I had originally entered the string as "c:\program
files\notepad++\notepad++.exe" "%F"

Was able to duplicate this by putting the errant string into the external
text editor box.

Another one of life's little mysteries solved - Oppie
Re: External text editor - again [message #135856 is a reply to message #135839] Thu, 17 February 2011 08:35 Go to previous messageGo to next message
Klaus Schmidinger
Messages: 1460
Registered: November 2008
Senior Member
On 02/16/11 16:26, Oppie wrote:
> Had a crash on my machine last week. All the important stuff was backed up
> so just an annoyance... Lost a few configuration files.
>
> Went to re-install Eagle 5.11 and set Notpad++ as my external editor. Was
> making me absolutely crazy as I would enter the path and next time the
> program opened, path was corrupted.
>
> This is what finally worked (copied from eaglerc but entered from control
> panel - Options - User interface). note that the eaglerc entry has an extra
> set of quote marks bounding the entire string.
> Interface.ExternalTextEditor = ""c:\Program Files\Notepad++\Notepad++.exe"
> "%F""
>
> Every time opened Eagle, the editor string was showing \ otepad++...
>
> Finally realized that Case was **important**
> I had originally entered the string as "c:\program
> files\notepad++\notepad++.exe" "%F"
>
> Was able to duplicate this by putting the errant string into the external
> text editor box.
>
> Another one of life's little mysteries solved - Oppie

Well, (ab)using the backslash ('\', which originally is an "escape" character)
as the directory delimiter is one of Microsoft's "original sins" ;-)
The others are using "\r\n" (two separate bytes, 0x0D/0x0A) instead of
a single '\n' (0x0A) as the line delimiter, and using the forward slash
as the "option" marker instead of the dash ('-').

Oh well...

Klaus Schmidinger
--
_______________________________________________________________

Klaus Schmidinger Phone: +49-8635-6989-10
CadSoft Computer GmbH Fax: +49-8635-6989-40
Pleidolfweg 15 Email: <private_email>
D-84568 Pleiskirchen, Germany URL: www.cadsoft.de
_______________________________________________________________
Re: External text editor - again [message #135857 is a reply to message #135856] Thu, 17 February 2011 08:51 Go to previous messageGo to next message
Tilmann Reh
Messages: 2068
Registered: October 2004
Senior Member
Klaus Schmidinger schrieb:

> Well, (ab)using the backslash ('\', which originally is an "escape" character)
> as the directory delimiter is one of Microsoft's "original sins" ;-)
> The others are using "\r\n" (two separate bytes, 0x0D/0x0A) instead of
> a single '\n' (0x0A) as the line delimiter, and using the forward slash
> as the "option" marker instead of the dash ('-').

I think these other two have much longer histories than Microsoft
itself, and every OS had its own separators those days. (For example, in
CP/M the options started with square brackets.) The CRLF pair as line
delimiter is really old and has its cause (teletypes would only feed a
line, but won't start at its beginning, if given just the LF).

In fact you feel the "right" way of doing something is the way you are
used to, and your background obviously are *ix systems and their
conventions.

However, I agree that using the backslash as directory delimiter
*really* is a sin - as is using case sensitivity in *ix systems and the
C programming language. These "broken by design" details, however, will
persist - it's far too late to change them now. :-\

Tilmann
Re: External text editor - again [message #135877 is a reply to message #135857] Thu, 17 February 2011 20:47 Go to previous messageGo to next message
Oppie[2]
Messages: 193
Registered: April 2009
Senior Member
"Tilmann Reh" <<private_email>> wrote in message
news:ijinj4$rnn$<private_email>...
> Klaus Schmidinger schrieb:
<snip>

I see you are both old timers in the business also. Brought a smile to my
face. Escape characters, CP/M and Teletypes... Think I'll read my intel
i8008 programming/design manual again for old time's sake.
Cheers
Re: External text editor - again [message #149245 is a reply to message #135839] Mon, 28 January 2013 10:05 Go to previous messageGo to next message
Keith Barratt
Messages: 1
Registered: January 2013
Junior Member
I'm using Eagle 6.3.0 and I've just had a similar problem but the solution given by the OP did not work for me when accessing the setting via the 'Control Panel window -> Options -> User Interface ->External Text editor' setting
I ran into problems with the %F quotes.
In the end I used:
"C:\Program Files (x86)\Notepad++\notepad++.exe" %F
with no extra quotes
Cheers,
Keith
Re: External text editor - again [message #169746 is a reply to message #149245] Sun, 26 February 2017 06:41 Go to previous message
Paul Cavanagh
Messages: 4
Registered: February 2017
Junior Member
Using Sublime text editor as an external editor in eaglecad use the following including quotes and "%F" for file opening.


for macs

"/Applications/Sublime Text.app" "%F"

--
To view any images and attachments in this post, visit:
https://www.element14.com/community/message/216872
Previous Topic: Best way to do an odd shaped through-hole pad?
Next Topic: Unable to name polygon
Goto Forum:
  


Current Time: Fri Jul 28 16:49:24 GMT 2017