From: Tassilo Horn <tassilo@member.fsf.org>
To: Dave Pearson <davep@davep.org>
Cc: ding@gnus.org
Subject: Re: Following boxquote links in a message buffer borkes it!
Date: Fri, 08 May 2009 20:16:05 +0200 [thread overview]
Message-ID: <87d4ajtq8q.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87iqkbo6zn.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 08 May 2009 19:10:52 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
Hi Reiner,
>> I wasn't sure if this is a boxquote, gnus or a combination of both
>> problem, so here we go.
>
> Try to reproduce it in *scratch*. -> The same. Then it's independent
> from Gnus.
Indeed, there it's the same. Another observation: The *Help* buffer has
the same contents like *scratch* after following the link.
>> the two functions are undelined and I can click them (or hit RET on
>> them) to get the function's docstring. Unfortunately this is not
>> done in the *Help* buffer, but instead the current buffer (*mail* in
>> this case) is erased and the help contents are inserted. Then the
>> buffer is read-only and I cannot undo, thus my mail is lost.
>
> Duh!
>
> `boxquote.el' should probably strip the properties before inserting
> the text.
Well, I like the possibility to click those links. It simply should
open them in *Help* solely without modifying the current buffer.
Dave, maybe you could provide a simple test case which produces a link
like those in boxquotes?
Bye,
Tassilo
next prev parent reply other threads:[~2009-05-08 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 11:42 Tassilo Horn
2009-05-08 17:10 ` Reiner Steib
2009-05-08 18:16 ` Tassilo Horn [this message]
2009-05-08 20:53 ` Reiner Steib
2009-05-08 22:19 ` Tassilo Horn
2009-05-09 10:32 ` Reiner Steib
2009-05-09 12:14 ` Andreas Schwab
2009-05-10 20:07 ` Dave Pearson
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=87d4ajtq8q.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=davep@davep.org \
--cc=ding@gnus.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 NNTP newsgroup(s).