GNU bug report logs - #3080
23.0.92; emacsclient can not open frame without visiting file

Previous Next

Package: emacs;

Reported by: Jameson Rollins <jrollins <at> finestructure.net>

Date: Wed, 22 Apr 2009 16:00:03 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Jameson Rollins <jrollins <at> finestructure.net>
To: Dan Nicolaescu <dann <at> ics.uci.edu>
Cc: 3080 <at> debbugs.gnu.org, rfrancoise <at> debian.org
Subject: bug#3080: 23.0.92; emacsclient can not open frame without visiting file
Date: Wed, 22 Apr 2009 17:38:55 -0700
[Message part 1 (text/plain, inline)]
On Wed, Apr 22, 2009 at 02:25:04PM -0700, Dan Nicolaescu wrote:
> Jameson Rollins <jrollins <at> finestructure.net> writes:
> 
>   > emacsclient does not allow for opening a frame, either in a terminal
>   > or in a new X frame, with*out* touching a file.  This is maybe only an
>   > issue when emacs is run in --daemon mode where an initial frame is not
>   > created.  It is often useful to open up an emacs without having a
>   > particular file that needs to be editted, and this is not currently
>   > possible.  In fact, I would prefer to see emacsclient behave more like
>   > the "classical" emacs behaves.  I would like to see the following
>   > behavior, that I think makes more sense and is more compatible with
>   > the classic interface:

Hi, Dan.  Thanks for the response.  What I was trying to outline below
was partially whether the functionality worked or not, but also that
the emacsclient interface is different that the standard emacs
interface, and that this seems a little bit unfortunate, seeing as
they could be the same.  Would it be possible to have them be the
same?  I think it would make interacting with the server/client much
easier.

>   > emacsclient
>   >   opens up a new frame with *scratch*
> does not work, it seems intentional, no idea why.

This is also the main thing that I was having issue with not working.
Is there any reason the behavior of just having emacsclient called
without any arguments open up an empty frame can't be supported?

jamie.

>   > emacsclient <file>
>   >   opens up a new frame with <file>
> 
> emacsclient -c <file>
> does this
> 
> 
>   > emacsclient -nw
>   >   opens up a new frame in the current terminal with *scratch*
> 
> this works
> 
>   > emacsclient -nw <file>
>   >   opens up a new frame in the current terminal with <file>
> 
> this works
> 
>   > emacsclient -<?> <file>
>   >   opens up <file> in an already opened "master" frame
> 
> emacsclient <file> 
> does this
> 
> 
[signature.asc (application/pgp-signature, attachment)]

This bug report was last modified 16 years and 33 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.