From: Jameson Rollins <jrollins@finestructure.net>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 3080@emacsbugs.donarmstrong.com, rfrancoise@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 [thread overview]
Message-ID: <20090423003855.GK7931@finestructure.net> (raw)
In-Reply-To: <200904222125.n3MLP4kN008572@godzilla.ics.uci.edu>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
On Wed, Apr 22, 2009 at 02:25:04PM -0700, Dan Nicolaescu wrote:
> Jameson Rollins <jrollins@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
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2009-04-23 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 15:54 bug#3080: 23.0.92; emacsclient can not open frame without visiting file Jameson Rollins
2009-04-22 20:42 ` Andreas Schwab
2009-04-22 21:25 ` Dan Nicolaescu
2009-04-23 0:38 ` Jameson Rollins [this message]
2009-04-23 2:33 ` Dan Nicolaescu
2009-04-23 15:02 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090423003855.GK7931@finestructure.net \
--to=jrollins@finestructure.net \
--cc=3080@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
--cc=rfrancoise@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).