[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Buffer names are sometimes read-only objects in daemonized emacs
|
From: |
Johan Bockgård |
|
Subject: |
Re: Buffer names are sometimes read-only objects in daemonized emacs |
|
Date: |
Sat, 31 Jul 2010 01:35:20 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>> 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?
- Re: How do I debug errors in post-command-hook?, (continued)
- Re: How do I debug errors in post-command-hook?, Tassilo Horn, 2010/07/30
- Re: How do I debug errors in post-command-hook?, Johan Bockgård, 2010/07/30
- 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
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Johan Bockgård, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Tassilo Horn, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Wojciech Meyer, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Tassilo Horn, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Wojciech Meyer, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Stefan Monnier, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Lennart Borgman, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs,
Johan Bockgård <=