From: Yuri Khan <yuri.v.khan@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Etymology of `visiting' files
Date: Mon, 8 Aug 2016 18:36:34 +0600 [thread overview]
Message-ID: <CAP_d_8VEp7TYdOxhjm06AFm+nP4Lq87bnTT1a_5WGSQmRmhPFg@mail.gmail.com> (raw)
In-Reply-To: <874m6vlefc.fsf@kuiper.lan.informatimago.com>
On Mon, Aug 8, 2016 at 5:53 PM, Pascal J. Bourguignon
<pjb@informatimago.com> wrote:
>> What motivated the choice of the verb `visiting'?
>> my own expectation would have been something like `edit' or `load'
The word “edit” implies a one-time change.
The word “load” implies creating an in-memory copy of the whole file.
> 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.
When you visit a friend’s home, you enter a small part of it, and you
may touch and change something in your immediate vicinity, or you can
explore different parts of the house.
The word “visit” might, at some time in the past, have meant getting
in position to perform modifications *without loading* the whole file
into memory. This could be an important factor when files were big and
memory was small. The changes could then be accumulated in memory as a
diff, small enough to fit in memory, to be applied on file save.
I do not know if this kind of memory use optimization has ever existed
in Emacs. But it might have, or it might have been considered a
future-in-the-past idea good enough to affect the terminology.
Of course, nowadays we have 64-bit address space and more virtual
memory than is ever necessary to edit any reasonably sized file (with
the notable exception of /dev/sda), so we can afford “loading” files.
next prev parent reply other threads:[~2016-08-08 12:36 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
2016-08-08 12:36 ` Yuri Khan [this message]
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=CAP_d_8VEp7TYdOxhjm06AFm+nP4Lq87bnTT1a_5WGSQmRmhPFg@mail.gmail.com \
--to=yuri.v.khan@gmail.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).