From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Etymology of `visiting' files
Date: Mon, 08 Aug 2016 12:53:43 +0200 [thread overview]
Message-ID: <874m6vlefc.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 87y447oaaw.fsf@rudiments.goosenet.in
Udyant Wig <udyant@rudiments.goosenet.in> writes:
> What motivated the choice of the verb `visiting'?
>
> From reading some of the relevant section in the Emacs and Elisp
> manuals, I understand the process the verb names. However, I wanted to
> find some reasoning or discussion about the choice of verb; my own
> expectation would have been something like `edit' or `load', but that
> would be looking through the lens provided by recent editing systems.
When you visit a friend's home, you enter it, you can look around, and
you may touch and change something (move a vase from the table to the
console) or not, and then leave the house.
Same with files.
visit = (or edit load)
edit implies some mutation.
load implies no mutation.
When you visit, you can do either.
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next prev parent reply other threads:[~2016-08-08 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 9:54 Etymology of `visiting' files Udyant Wig
2016-08-08 10:53 ` Pascal J. Bourguignon [this message]
2016-08-08 12:36 ` Yuri Khan
2016-08-08 12:37 ` Narendra Joshi
2016-08-08 12:48 ` Florian v. Savigny
2016-08-09 5:17 ` Udyant Wig
2016-08-08 13:58 ` Ted Zlatanov
2016-08-09 5:37 ` Udyant Wig
2016-08-09 15:37 ` Barry Margolin
2016-08-10 9:24 ` Etymology of `visiting' files, and for that matter, of `finding' them Florian v. Savigny
2016-08-08 19:36 ` Etymology of `visiting' files Robert Thorpe
-- strict thread matches above, loose matches on Subject: below --
2016-08-09 6:42 Udyant Wig
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=874m6vlefc.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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.
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).