all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Buffer names are sometimes read-only objects in daemonized emacs
Date: Mon, 02 Aug 2010 01:10:56 +0200	[thread overview]
Message-ID: <jwvtyne6iba.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k4ocy24n.fsf@gnu.org> ("Johan Bockgård"'s message of "Sat, 31 Jul 2010 01:35:20 +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.
> Should `put-text-property' do that too?

Probably, but that will break a lot more packages (removing the "aset on
strings" feature breaks fairly few packages, surprisingly enough).


        Stefan



      reply	other threads:[~2010-08-01 23:10 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
2010-07-30 23:35                   ` Johan Bockgård
2010-08-01 23:10                     ` Stefan Monnier [this message]

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=jwvtyne6iba.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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.
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.