[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS; gnuserv -- Allows you to attach to an already running Emacs

I'm  not the maintainer, but still:

On Sat, Oct 21, 2006 at 10:55:52PM +0200, Jens Peter Secher wrote:

> - Why do you do a 'dh_installemacsen --flavor=emacs21' instead of just
> 'dh_installemacsen' in debian.rules?  Is it because gnuserv is not
> needed for xemacs?

xemacs comes with its own gnuserv; I think the package is actually
xemacs's gnuserv ripped out from the xemacs codebase and ported to FSF

> - When I do a 'gnuclient somefile', I get a new Emacs _window_, not
> just a new buffer in the one already running.  It seems somewhat
> confusing...

It has been that way for months/years. It permits to use gnuclient
even if the gnuserv-running emacs is on another X display, and has no
frame yet on the X display you are currently using. One could imagine
that gnuclient opens a new frame only if no frame is already present
on said display, but as a user I would strongly object to gnuclient
reusing a frame on a display I cannot currently see! This includes not
only frames on a different X display than the one I'm using, but also
frames on a different viewport / workspace / a currently non-visible
portion of the workspace. I wouldn't enjoy having to hunt down which
of my existing emacs frames on my four workspaces got the file opened
(which is something that galeon forces me to do, the main reason I
have changed Gnome's URL handler to be "galeon -w"). So a new frame
that my window manager will put where I will see it looks actually
better to me than reusing another frame and getting subcases wrong.


Reply to: