unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15335@debbugs.gnu.org
Subject: bug#15335: emacs -Q usability
Date: Wed, 12 Aug 2020 15:44:42 -0700	[thread overview]
Message-ID: <CADwFkmmZ_06ZM-BAfmcLGm58d1GLymExhCaJOkSJBqYJteQevA@mail.gmail.com> (raw)
In-Reply-To: <835zh2t5aq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 Jan 2020 20:07:41 +0200")

tags 15335 + wontfix
close 15335
thanks

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Thu, 23 Jan 2020 14:21:39 +0100
>> Cc: 15335@debbugs.gnu.org
>>
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>> > Emacs -Q opening with scratch buffer is a mistake in most cases.
>> >
>> > Please make Emacs star as general purpose Editor, preferably with an empty buffer,
>> > in text- or fundamental mode, where use may see it's input, being offered to save it etc.
>> >
>> > See also
>> >
>> > http://stackoverflow.com/questions/18734848/choosing-an-all-purpose-editor/18735853
>>
>> Do new users generally run "emacs -Q" though?  I would have assumed
>> that they either just run "emacs" (probably from a menu somewhere), or
>> "emacs <file>".
>
> I think this horse has been beaten ad nauseam, and every time we
> discussed it, we decided to keep the current behavior.  It's time to
> put this to rest, IMO.

OK, since there has been no further comments within 28 weeks, I'm
closing this bug as wontfix.

Best regards,
Stefan Kangas





      reply	other threads:[~2020-08-12 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11  8:50 bug#15335: emacs -Q usability Andreas Röhler
2013-09-11 14:17 ` Drew Adams
2013-09-11 14:57   ` Andreas Röhler
2020-01-23 13:21 ` Stefan Kangas
2020-01-23 18:07   ` Eli Zaretskii
2020-08-12 22:44     ` Stefan Kangas [this message]

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=CADwFkmmZ_06ZM-BAfmcLGm58d1GLymExhCaJOkSJBqYJteQevA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=15335@debbugs.gnu.org \
    --cc=eliz@gnu.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).