Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: MIME button mystery
Date: Fri, 19 Aug 2011 17:52:04 +0900	[thread overview]
Message-ID: <b4mbovl237v.fsf@jpl.org> (raw)
In-Reply-To: <b4mmxf529it.fsf@jpl.org>

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

Katsumi Yamaoka wrote:
> If you use Gnus to read this article, please try:

> Type `M-t' in the summary buffer to make MIME buttons visible.
> In the article buffer, put the cursor under a MIME button.
> Type the `E' key.

> And you will get: Wrong type argument; stringp, nil


[-- Attachment #2: Type: text/plain, Size: 498 bytes --]

> Why this happens is that the keymap there is the one for the MIME
> buttons, not the article commands, in spite of outside the button
> (`C-h c E' there tells that the `E' key is bound to the command
> `gnus-mime-view-part-internally'), but there is no handle data
> associated with the button above.

> What provides the MIME buttons keymap there?  There is neither a
> text property nor an overlay that provides a local map, so the
> keymap used there should be that for the article commands.


[-- Attachment #3: Type: text/plain, Size: 394 bytes --]

I found the cause of this behavior in the `keymap' section of
(info "(Elisp)Special Properties"):
     The property's value for the character before point applies if it
     is non-`nil' and rear-sticky, and the property's value for the
     character after point applies if it is non-`nil' and front-sticky.

So, I've made changes so as to add the (rear-nonsticky t) property
to MIME buttons.

      reply	other threads:[~2011-08-19  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  6:35 Katsumi Yamaoka
2011-08-19  8:52 ` Katsumi Yamaoka [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=b4mbovl237v.fsf@jpl.org \
    --to=yamaoka@jpl.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).