Read-only message separator

Read-only message separator

[Michael Piotrowski]

Hi,

The change in `message-setup-1' to insert the mail-header-separator with
read-only and intangible properties set (commit
bd10f37e4630719920f82122d7c7ae7523567762) doesn't work for me (on XEmacs
21.4.22).  When trying to compose a message, I get

#v+
Debugger entered--Lisp error: (buffer-read-only #<buffer "*unsent mail*">)
  insert("")
  (progn (insert message-default-mail-headers) (or (bolp) (insert ?\n)))
  (if message-default-mail-headers (progn (insert message-default-mail-headers) (or ... ...)))
  (when message-default-mail-headers (insert message-default-mail-headers) (or (bolp) (insert ?\n)))
  (progn (when message-default-mail-headers (insert message-default-mail-headers) (or ... ...)) (message-generate-headers (message-headers-to-generate ... message-generate-headers-first ...)))
  (if (message-mail-p) (progn (when message-default-mail-headers ... ...) (message-generate-headers ...)))
  (when (message-mail-p) (when message-default-mail-headers (insert message-default-mail-headers) (or ... ...)) (message-generate-headers (message-headers-to-generate ... message-generate-headers-first ...)))
  (let ((message-generate-headers-first ...)) (when (message-news-p) (when message-default-news-headers ... ...) (message-generate-headers ...)) (when (message-mail-p) (when message-default-mail-headers ... ...) (message-generate-headers ...)))
  message-setup-1(((To . "") (Subject . "")) nil nil nil)
  message-setup(((To . "") (Subject . "")) nil nil nil nil nil)
  message-mail()
  gnus-group-mail(nil)
  call-interactively(gnus-group-mail)
#v-

It works if I change

  'read-only t

to

  'read-only nil

in the call to `propertize' in `message-setup-1'.

An XEmacs issue?

Thanks and greetings

-- 
Dr.-Ing. Michael Piotrowski, M.A.                   <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)

Re: Read-only message separator

[Lars Ingebrigtsen]

Michael Piotrowski <mxp@dynalabs.de> writes:

> It works if I change
>
>   'read-only t
>
> to
>
>   'read-only nil
>
> in the call to `propertize' in `message-setup-1'.
>
> An XEmacs issue?

So you can't insert read-only strings into buffers in XEmacs?  That
sounds...  annoying...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Read-only message separator

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So you can't insert read-only strings into buffers in XEmacs?  That
> sounds...  annoying...

If I eval:

(insert (propertize (concat mail-header-separator "\n")
		    'read-only t 'rear-nonsticky t 'intangible t))

in XEmacs, it works as you'd expect.  It inserts a read-only string.  So
I don't seem to be able to reproduce this bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Read-only message separator

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> in XEmacs, it works as you'd expect.  It inserts a read-only string.  So
> I don't seem to be able to reproduce this bug.

Actually, when using XEmacs on this function, it breaks badly, and I
have no idea why.  I've reverted the change for the moment, but we
should investigate why it fails and reinstate the read-onlyness.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Read-only message separator

[Michael Piotrowski]

On 2011-02-04, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> in XEmacs, it works as you'd expect.  It inserts a read-only string.  So
>> I don't seem to be able to reproduce this bug.
>
> Actually, when using XEmacs on this function, it breaks badly, and I
> have no idea why.

Right, as such inserting the separator works, but apparently there is
some interaction in `message-setup-1'.

> I've reverted the change for the moment, but we should investigate why
> it fails and reinstate the read-onlyness.

Thanks.  It's very annoying if you can't even write messages ...

Best regards

-- 
Dr.-Ing. Michael Piotrowski, M.A.                   <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)

Re: Read-only message separator

[Ted Zlatanov]

On Sat, 05 Feb 2011 10:42:06 +0100 Michael Piotrowski <mxp@dynalabs.de> wrote: 

MP> On 2011-02-04, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> 
>>> in XEmacs, it works as you'd expect.  It inserts a read-only string.  So
>>> I don't seem to be able to reproduce this bug.
>> 
>> Actually, when using XEmacs on this function, it breaks badly, and I
>> have no idea why.

MP> Right, as such inserting the separator works, but apparently there is
MP> some interaction in `message-setup-1'.

>> I've reverted the change for the moment, but we should investigate why
>> it fails and reinstate the read-onlyness.

MP> Thanks.  It's very annoying if you can't even write messages ...

Can it be conditionally enabled just for non-XEmacs users while the
investigation proceeds?

Ted

Re: Read-only message separator

[Lars Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> Can it be conditionally enabled just for non-XEmacs users while the
> investigation proceeds?

We could, but I think it would be better to just find out why it fails
on XEmacs and just fix it.  :-)

Any takers?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Read-only message separator

[Ted Zlatanov]

On Sun, 13 Feb 2011 19:20:05 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Can it be conditionally enabled just for non-XEmacs users while the
>> investigation proceeds?

LI> We could, but I think it would be better to just find out why it fails
LI> on XEmacs and just fix it.  :-)

LI> Any takers?

I'm not touching XEmacs after it rewrote my custom.el file without
asking this weekend.

Ted

Re: Read-only message separator

[Julien Danjou]

[-- Attachment #1: Type: text/plain, Size: 272 bytes --]

On Mon, Feb 14 2011, Lars Ingebrigtsen wrote:

> Any takers?

It seems not. Maybe letting this broken will motivate someone to either
fix it/XEmacs (don't know which one fault it is), or switch to GNU
Emacs? ;-)

-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Read-only message separator

[Lars Ingebrigtsen]

Julien Danjou <julien@danjou.info> writes:

> It seems not. Maybe letting this broken will motivate someone to either
> fix it/XEmacs (don't know which one fault it is), or switch to GNU
> Emacs? ;-)

:-)

It's not very neighbourly...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen