unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: *scratch* buffer documentation
Date: Fri, 27 Dec 2019 03:14:11 +0900	[thread overview]
Message-ID: <E8E2D14D-D862-4A97-ABEE-F3EE7A6973A6@traduction-libre.org> (raw)
In-Reply-To: <87h81n2dl2.fsf@gnus.org>



> On Dec 27, 2019, at 2:36, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> 
> Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
> writes:
> 
>> I just tried something:
>> 
>> create a buffer, type something, kill Emacs.
>> 
>> Of course, when I restarted Emacs the buffer was gone.
>> 
>> In any other editor I'd either have a warning that I'm going to lose
>> data or the data would have been automatically saved and would be
>> restored when I restarted the editor.
> 
> Are there any other editors where you can open a "buffer" that's not
> associated with a file?

As far as *UX* is concerned (I'm not concerned about the internals), pretty much all the editors I use. Including the most basic macos TextEdit.

When you create a new "file" it is just a "buffer" and is not associated to any material file at that point. And TextEdit will keep the data even if the file is not created/saved even if TextEdit is "killed" and restarted.

The cool (?) thing about Emacs is that you can do the same thing in 2 ways:
create a buffer
visit a non existing *file*

when you modify and then kill the two without saving, in one case the data is gone, in the other case Emacs does not ask you whether you worry about the contents of the *file* or not, but whether you worry about the *buffer*...

So the main difference in Emacs is that either you start by saying you want to associate the buffer to a file, or you finish by saying that. That is a complication that does not exist in (most) other editors.

But as far as the user is concerned (and users now have the possibility to have a lot of experience outside the Emacs realm before coming here, or while using Emacs) it is not fundamentally different, and not different from what they experience outside Emacs, especially since the nature of a buffer is not properly explained.

> Most people use editors to edit files,

I don't know that. I know that I'd paste a big bunch of data into an open window in BBEdit and do regex search replaces and then paste the results back to wherever I need it, and that window will never be saved to a file. I use TextEdit like that plenty of the time too. There is a lot of transient information that will be reshuffled to various applications and I just need a place to type a few things. But I know that contrary to Emacs, such transient data is mostly safe in other applications.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune





  reply	other threads:[~2019-12-26 18:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 23:58 *scratch* buffer documentation Jean-Christophe Helary
2019-12-25  1:24 ` Óscar Fuentes
2019-12-25  1:44   ` Jean-Christophe Helary
2019-12-25 14:55 ` Eli Zaretskii
2019-12-26  0:54   ` Jean-Christophe Helary
2019-12-26  2:29     ` arthur miller
2019-12-26  3:00       ` Jean-Christophe Helary
2019-12-26  3:27         ` Óscar Fuentes
2019-12-26  5:19           ` Jean-Christophe Helary
2019-12-26  5:20           ` Jean-Christophe Helary
2019-12-26 16:22     ` Eli Zaretskii
2019-12-26 17:15       ` Jean-Christophe Helary
2019-12-26 17:36         ` Lars Ingebrigtsen
2019-12-26 18:14           ` Jean-Christophe Helary [this message]
2019-12-26 20:25         ` Eli Zaretskii
2019-12-27  1:03           ` Jean-Christophe Helary
2019-12-27  8:12             ` Eli Zaretskii
2019-12-27  9:12               ` Jean-Christophe Helary
2019-12-27  9:26                 ` Eli Zaretskii
2019-12-27  9:44                   ` Jean-Christophe Helary
2019-12-27 11:31               ` VanL
2019-12-27 14:06                 ` Eli Zaretskii
2019-12-27 18:24                   ` John Yates
2019-12-27 18:45                     ` Eli Zaretskii
2019-12-27 16:12               ` Drew Adams
2019-12-27 17:07               ` Lars Ingebrigtsen

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=E8E2D14D-D862-4A97-ABEE-F3EE7A6973A6@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --cc=emacs-devel@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).