From: James Nguyen <jamesn@fastmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 27511@debbugs.gnu.org
Subject: bug#27511: 26.0.50; emacsclient requires file argument
Date: Wed, 28 Jun 2017 08:00:45 -0700 [thread overview]
Message-ID: <E45DAD87-0802-4C81-934E-2476AFD7BF87@fastmail.com> (raw)
In-Reply-To: <CAM-tV---BXmzgBRCBt6cZ=2fVn8Nkm4-1Sx_NwAC+aHB6H7frA@mail.gmail.com>
"Emacs simply displays those files; otherwise, it displays a buffer named *scratch*, which can be used to evaluate Emacs Lisp expressions interactively."
I think it’s preferable it behaves just like regular ‘emacs’ does, opening a *scratch* buffer as a fallback.
> On Jun 28, 2017, at 7:45 AM, Noam Postavsky <npostavs@users.sourceforge.net> wrote:
>
> On Tue, Jun 27, 2017 at 10:03 PM, James Nguyen <jamesn@fastmail.com> wrote:
>>
>> Running emacsclient without specifying a file results in:
>>
>> emacsclient: file name or argument required
>> Try 'emacsclient --help' for more information
>>
>> https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html#Entering-Emacs
>>
>> Gives the impression *scratch* should show up instead. (though probably
>> only if running 'emacs' regularly.)
>
> Which part gives you that impression? Or in other words, what do you
> want to change?
next prev parent reply other threads:[~2017-06-28 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 2:03 bug#27511: 26.0.50; emacsclient requires file argument James Nguyen
2017-06-28 14:45 ` Noam Postavsky
2017-06-28 15:00 ` James Nguyen [this message]
2017-06-28 17:03 ` Ken Brown
2017-06-28 17:22 ` James Nguyen
2017-06-28 17:35 ` Noam Postavsky
2017-06-28 23:49 ` James Nguyen
2017-06-29 1:13 ` npostavs
2017-06-29 3:35 ` James Nguyen
2017-06-29 12:32 ` npostavs
2017-06-29 14:11 ` Ken Brown
2017-06-29 16:48 ` James Nguyen
2017-06-29 18:11 ` Ken Brown
2017-06-30 1:06 ` James Nguyen
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=E45DAD87-0802-4C81-934E-2476AFD7BF87@fastmail.com \
--to=jamesn@fastmail.com \
--cc=27511@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).