unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: One-off history for read-string
Date: Sun, 27 Sep 2015 03:20:51 +0200	[thread overview]
Message-ID: <87612wr72k.fsf@debian.uxu> (raw)
In-Reply-To: 87h9mhbp26.fsf@mbork.pl

Marcin Borkowski <mbork@mbork.pl> writes:

> From Emacs' point of view, it's kind of read-only;
> while read-string does write to it, it _doesn't
> matter_ at all. But you can call it what you want.
> I'm not very good at naming things, apparently.

It is not a good policy to name things after
properties that doesn't matter.

Also, most often it is not a good idea to name things
in terms of technology but rather their
purpose/usefulness, but there are more and more
exceptions to that rule the deeper you delve into
technology and this might be one of them.

This is client-server/remote/distributed history.

>> And how will the history be assembled if it is only
>> clients that fetch it and then never add to it?
>
> Who said about never adding? ... Of course it is
> sent to the server, by some _other_ piece of code.

Then it is even more confusing to call it "read only"
as both writing and reading is done.

> and there is _no point_ in keeping the history in
> two places

Still, there is no gain removing it unless it does
any harm.

>> And again, what is the purpose of all this?
>
> To write an actual program which does something
> actually useful, not to discuss endlessly about why
> anyone might want to write such a program.

I don't ask in general, I specifically ask why you
want a server to handle the history?

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2015-09-27  1:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 12:10 One-off history for read-string Marcin Borkowski
2015-09-24 15:47 ` Stefan Monnier
2015-09-24 16:27   ` Marcin Borkowski
2015-09-24 17:04     ` Drew Adams
2015-09-25  0:34 ` Emanuel Berg
2015-09-25  7:16   ` Marcin Borkowski
2015-09-26  2:02     ` Emanuel Berg
2015-09-26  2:33       ` John Mastro
2015-09-26  2:47         ` Emanuel Berg
2015-09-26  7:46           ` Marcin Borkowski
2015-09-27  1:20             ` Emanuel Berg [this message]
2015-09-27  6:02               ` Marcin Borkowski
2015-09-27 23:14                 ` Emanuel Berg
2015-09-28  0:50             ` Stefan Monnier
2015-09-26  7:46         ` Marcin Borkowski

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=87612wr72k.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).