Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: probem with mime parts face
Date: Tue, 05 Jun 2007 20:43:25 +0900	[thread overview]
Message-ID: <b4m7iqieiea.fsf@jpl.org> (raw)
In-Reply-To: <b4mmyzg0zps.fsf@jpl.org>

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

>>>>> In <b4mmyzg0zps.fsf@jpl.org> Katsumi Yamaoka wrote:
>>>>>> In <87hcpreb4c.fsf@poczta.po.opole.pl> Seweryn Kokot wrote:

>> I have an email with 6 parts (text/plain). In Article buffer I type K b
>> to distinguish them and have button for each file. Then I type RET on a
>> button which hides the text and after typing again RET I get the text
>> but with different foreground face of the text, namely
>> boldface. Preferably this action should not change the face of the
>> text. Is it a bug? I'm using Gnus v5.11 under Debian Unstable

>> Any idea?

[...]

> I don't know why the `widget-button' face is not inherited to
> the inserted text part.

Because `widget-specify-button' sets the fourth argument of
`make-overlay' when making a button.

,----
| (make-overlay beg end &optional buffer front-advance rear-advance)
|
| [...]
| The fourth arg front-advance, if non-nil, makes the marker
| for the front of the overlay advance when text is inserted there
| (which means the text *is not* included in the overlay).
`----

I've made a change in the trunk so that `gnus-insert-mime-button'
may do the same.  Probably I've solved the problem.

If you are hard to update Gnus everyday ;-p, you can use the
following instead temporarily in your ~/.gnus.el file:


[-- Attachment #2: Type: application/emacs-lisp, Size: 169 bytes --]

  reply	other threads:[~2007-06-05 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 19:19 Seweryn Kokot
2007-06-04 10:40 ` Katsumi Yamaoka
2007-06-05 11:43   ` Katsumi Yamaoka [this message]
2007-06-05 20:56     ` Seweryn Kokot

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=b4m7iqieiea.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).