From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Buffer names are sometimes read-only objects in daemonized emacs
Date: Mon, 02 Aug 2010 01:09:55 +0200 [thread overview]
Message-ID: <jwvzkx66icz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTinoPv=_TJYqj=QchHvvc9r0n8HhcLHHKNybfKaU@mail.gmail.com> (Lennart Borgman's message of "Sat, 31 Jul 2010 00:07:22 +0200")
>>> No no, you got me wrong. I just meant the docstring of `buffer-name'
>>> (and any other function that returns some thing whose modification would
>>> have undesired, non-obvious side-effects) should explicitly state that
>>> modifying that returned string will indeed modify the buffer name.
>> Rather, `aset' should warn that modifying strings is evil and dangerous.
> When will this aset be grown up enough to play outside of home?
Never (as in "not for the foreseeable future"), It would not bring any
benefit to the users, and would break backward compatibility: sound like
a clear loser to me.
Stefan
next prev parent reply other threads:[~2010-08-01 23:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 20:30 How do I debug errors in post-command-hook? Tassilo Horn
2010-07-29 21:33 ` Lennart Borgman
2010-07-30 0:11 ` Johan Bockgård
2010-07-30 6:54 ` Tassilo Horn
2010-07-30 11:58 ` Johan Bockgård
2010-07-30 14:23 ` Buffer names are sometimes read-only objects in daemonized emacs (was: How do I debug errors in post-command-hook?) Tassilo Horn
2010-07-30 17:46 ` Buffer names are sometimes read-only objects in daemonized emacs Johan Bockgård
2010-07-30 18:41 ` Tassilo Horn
2010-07-30 19:54 ` Wojciech Meyer
2010-07-30 20:08 ` Tassilo Horn
2010-07-30 20:46 ` Wojciech Meyer
2010-07-30 21:48 ` Stefan Monnier
2010-07-30 22:07 ` Lennart Borgman
2010-08-01 23:09 ` Stefan Monnier [this message]
2010-07-30 23:35 ` Johan Bockgård
2010-08-01 23:10 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzkx66icz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.