unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>, 15335@debbugs.gnu.org
Subject: bug#15335: emacs -Q usability
Date: Wed, 11 Sep 2013 07:17:00 -0700 (PDT)	[thread overview]
Message-ID: <116851da-a40d-4835-858c-cef0c8aa4b85@default> (raw)
In-Reply-To: <52302EEA.6090805@easy-emacs.de>

> Emacs -Q opening with scratch buffer is a mistake in most cases.
> Please make Emacs star[t] 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

I have some sympathy for this. However, which mode for that (presumably)
new-file buffer?  You say text mode or fundamental mode. Perhaps (text,
but not fundamental). But realistically, how much of the time does an Emacs
user use text mode?  Yes, the mode could be configurable by the user. 

But other editors often open with no such new file/buffer window.  TextPad
is a good example.  Just as for Emacs, you need to click the `New' icon to
open a new-file buffer.  Otherwise, it opens with just an empty editor frame.

Anyway, Emacs now provides multiple possibilities for the startup
appearance & behavior.  One of those is `initial-buffer-choice', which you
can customize to a file or directory name.  This should get you pretty much
what you are asking, I think.

But the question then is what the default startup should be like.  If
`initial-buffer-choice' were by default a `new' buffer name then that
should pretty much give you what you are asking for.

Personally, I think the default startup should be with Dired, in some
default directory that a user can trivially customize.  That gives a larger
perspective than does *scratch* or even a new-file buffer.  IOW, I'd vote
for `initial-buffer-choice' to be an existing directory name.





  reply	other threads:[~2013-09-11 14:17 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 [this message]
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

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=116851da-a40d-4835-858c-cef0c8aa4b85@default \
    --to=drew.adams@oracle.com \
    --cc=15335@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    /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).