Re: basic question: going back to dired
  Home FAQ Contact Sign in
gnu.emacs.help only
 
Advanced search
POPULAR GROUPS

more...

gnu.emacs.help Profile…
 Up
Re: basic question: going back to dired         


Author: Bastien
Date: Jul 21, 2008 16:21

Ben Aurel gmail.com> writes:
> My question is simple: When I list some files in dired mode I select one
> file to edit. Now how can I close this file and go back to dired without
> closing emacs?

Don't think in terms of "file". When editing a "file", you really edit
a buffer* containing the content of the file. To "close" the file
generally means to save the buffer and to kill the buffer.

If you just want to "go back" to dired, you just need to switch back to
the buffer containing the directory listing: C-x b RET

If you want to "close the file", then first save the buffer with C-x C-s
then kill the buffer with C-x k RET and you should be back to the buffer
containing the directory listing.

HTH,

* Press `C-x C-e' after the closing parenthesis to jump to the info page
describing the concept of "buffer" inside GNU Emacs:

(info "(emacs)Buffers")

--
Bastien
108 Comments
Re: basic question: going back to dired         


Author: Xah
Date: Jul 21, 2008 23:04

I don't think its a good idea to teach or insist that people adopt
emacs's terminologies.

In particular, the term buffer is unsuitable and outdated. See the
following argument:

----------------------------

Q: The Terminology “buffer” and “keybinding” is good as they are.

A:
The terminology “buffer” or “keybinding”, are technical terms having
to do with software programing. The term “keybinding” refers to the
association of a keystroke with a command in a technical, software
application programing context. That is to say, a programer “bind” a
keystroke event to a command in a software application. The term
“buffer” refers to a abstract, temporary area for storing data, in the
context of programing or computer science.

These terms are irrelevant to the users of a software application.
Show full article (3.55Kb)
5 Comments
Re: basic question: going back to dired         


Author: Bastien Guerry
Date: Jul 22, 2008 01:26

Xah gmail.com> writes:
> I don't think its a good idea to teach or insist that people adopt
> emacs's terminologies.

Adopting Emacs terminology is not good per se, it's good because it
helps people adopt Emacs.
> In particular, the term buffer is unsuitable and outdated. See the
> following argument:

You're arguing like a lawyer: since you cannot change the law itself,
you're just trying to change the spirit of the law.

Please improve Emacs if you want to, it will be more constructive than
trying to change the "spirit" behind Emacs...

--
Bastien
no comments
Re: basic question: going back to dired         


Author: Phil Carmody
Date: Jul 22, 2008 02:46

Xah gmail.com> writes:
> I don't think its a good idea to teach or insist that people adopt
> emacs's terminologies.

When discussing emacs? That's a rather bizarre thing to say.
Show full article (1.60Kb)
3 Comments
Re: basic question: going back to dired         


Author: Juanma Barranquero
Date: Jul 22, 2008 04:22

On Tue, Jul 22, 2008 at 11:46, Phil Carmody
yahoo.co.uk> wrote:
> Xah gmail.com> writes:
>> These terms are irrelevant to the users of a software application.
>
> Blatant assertion I disagree with completely.

In which way the use of terms like "keybinding" or "buffer" is
relevant to the *users* of a software application?
>> As a user of a text editor, he works with files.
>
> Blatant assertion I disagree with completely. As a user of a text
> editor, I work with text. And I want it neatly buffered for me.
> I may occasionally load some of the text from a file, and I may
> occasionally save some of the text to a file, but the majority
> of the buffers that I use never undergo either.

It is true that the user of a text editor works with text. It is also
true, I think, that most text is saved to a file, though nowadays I
suppose there's also a fair amount that is cut&paste'd into another
application, a web form, etc.
Show full article (1.41Kb)
no comments
Re: basic question: going back to dired         


Author: Juanma Barranquero
Date: Jul 22, 2008 04:29

On Tue, Jul 22, 2008 at 10:26, Bastien Guerry altern.org> wrote:
> Adopting Emacs terminology is not good per se, it's good because it
> helps people adopt Emacs.

Adapting Emacs terminology to current conventions would perhaps be
good for the very same reason.

I'm not for or against changing Emacs' terminology. I think it would
be a huge amount of work. But I don't understand why some people
reacts as if the very idea is flawed. There's nothing sacred in
"buffer" and "keybinding" and "minibuffer", just history. The change
should be susceptible to rational (if perhaps a bit pointless)
discussion, because it is not hard to find good arguments for it;
"frame/window" vs "window/pane" is a good example.

Juanma
no comments
Re: basic question: going back to dired         


Author: Phil Carmody
Date: Jul 22, 2008 04:50

"Juanma Barranquero" gmail.com> writes:
> On Tue, Jul 22, 2008 at 11:46, Phil Carmody
> yahoo.co.uk> wrote:
>> Xah gmail.com> writes:
>
>>> These terms are irrelevant to the users of a software application.
>>
>> Blatant assertion I disagree with completely.
>
> In which way the use of terms like "keybinding" or "buffer" is
> relevant to the *users* of a software application?

I, as a user of the software application called "emacs"
must be familiar with that functions are bound to what
keys in order to use that software application.

For buffers, see below.
Show full article (1.86Kb)
no comments
Re: basic question: going back to dired         


Author: Juanma Barranquero
Date: Jul 22, 2008 05:14

On Tue, Jul 22, 2008 at 13:50, Juanma wrote:
> And why should "shortcut" be more fitting than "keybinding"?

I don't know. I'm not even defending the idea that "shortcut" is more
fitting. If anything, I'm defending the idea that "keybinding" is not
very good, not because of any intrinsic quality or defect of the term
"keybinding", just because it is a bit too specifically emacsy for
something that many other programs allow, under a different name. The
best name is the one the users understand more easily (whichever it
may be).
> Emacs does lots more than text editing, and the term
> "buffer" fits fine for all the tasks, where term "file" doesn not.

The term "workspace" fits even better, don't you think? And, what does
think the average user who does intuitively know (I believe) what a
"work space" could be, but not necessarily what a "buffer" is?
> That is called "loosing generality", at least in Spanish, which you
> know.

In my Castilian Spanish it'd be more like "perder generalidad", but I
get your meaning ;-)
Show full article (2.18Kb)
4 Comments
Re: basic question: going back to dired         


Author: Miles Bader
Date: Jul 22, 2008 05:34

"Juanma Barranquero" gmail.com> writes:
>> And why should "shortcut" be more fitting than "keybinding"?
>
> I don't know. I'm not even defending the idea that "shortcut" is more
> fitting. If anything, I'm defending the idea that "keybinding" is not
> very good, not because of any intrinsic quality or defect of the term
> "keybinding"

It's not that "keybinding" is somehow extra good, it's that "shortcut"
is unusually bad.

The name "shortcut" in most apps carries the implication that it's
somehow an unusual method of invoking something, which is only used in
rare circumstances for the absolute most heavily used commands (in these
apps, the "usual" method is a menu entry). This is not true in emacs --
keybindings are heavily used, and are "normal".

-Miles

--
Yo mama's so fat when she gets on an elevator it HAS to go down.
1 Comment
Re: basic question: going back to dired         


Author: Nikolaj Schumacher
Date: Jul 22, 2008 05:50

Xah gmail.com> wrote:
> I don't think its a good idea to teach or insist that people adopt
> emacs's terminologies.

I don't think its a good idea to teach or insist that people learn
French before going to Paris. French is a language that has been
adopted by France in the 1530s when there really weren't any other other
languages around, except big mainframe languages like Latin. In the
20th century English developed as a
> The reason emacs uses the technical terminologies throughout is
> because when emacs started in the 1980s, there really isn't any other
> text editors or even software applications. And, emacs users are all
> computer scientists and programers.

I think it's a ridiculous idea to teach someone English before going to
Paris. Of course English is spoken pretty much everywhere in the world,
and it would arguably easier to stay in Paris if the
>
> In particular, the term buffer is unsuitable and outdated. See the
> following argument:
>
> ----------------------------
>
> Q: The Terminology “buffer” and “keybinding” is good as they are.
>
> A...
Show full article (4.52Kb)
no comments
1 2 3 4 5 6 7 8 9