This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Patch: external editor changes
- To: Tom Tromey <tromey at redhat dot com>
- Subject: Re: Patch: external editor changes
- From: Keith Seitz <keiths at cygnus dot com>
- Date: Tue, 2 Oct 2001 16:09:27 -0700 (PDT)
- cc: Insight List <insight at sourceware dot cygnus dot com>
On 2 Oct 2001, Tom Tromey wrote:
> There are 3 command line options:
>
> * --tclcommand, which sources a Tcl file
> * --enable-external-editor, which used to just set a boolean
> * --editor-command, the argument to this is a Tcl command to run
> (with certain arguments appended) to edit a file
>
> I changed it so --enable-external-editor is just ignored, --tclcommand
> is untouched, and --editor-command overrides the user's editor setting.
Aah. Okay, I guess I was curious about the warning dialog that's in there
mentioning "--tclcommand".
> Tom> +namespace eval Editor {
>
> Keith> Aside: why a namespace instead of a class?
>
> This seemed better because you can't instantiate Editor.
> I can change this if you want.
Hmm... Can one resource a tcl file that contains a namespace definition,
i.e., if I add another proc to this namespace, can I still resource the
source file. You certainly cannot do this with an itcl class. That would
be a good motivation behind leaving it a namespace.
I checked this, and indeed it does work. So I would leave it as is. We
should probably do the same with sessions and anything else we can do it
to which lives in a single file. You cannot do this with itcl classes.
> It contacts an already-running Emacs and tells it to edit a file.
> Run server-start in Emacs to start the Emacs side.
> I put `(server-start)' into my .emacs.
Aha! Found it with "gnuserv-start". Thanks!
Keith