unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: rmail-toggle-header problem
Date: Fri, 20 Feb 2009 21:59:05 +0900	[thread overview]
Message-ID: <E1LaUy9-0004rx-8d@etlken> (raw)
In-Reply-To: <u3ae9v7e7.fsf@gnu.org> (message from Eli Zaretskii on Fri, 20 Feb 2009 10:29:04 +0200)

In article <u3ae9v7e7.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > From: Kenichi Handa <handa@m17n.org>
> > Date: Fri, 20 Feb 2009 10:35:18 +0900
> > Cc: rms@gnu.org, emacs-devel@gnu.org
> > 
> > In article <1sbpsyf9y4.fsf@fencepost.gnu.org>, Glenn Morris <rgm@gnu.org> writes:
> > 
> > > I'm not sure that yanking from the full headers makes a lot of sense,
> > > though. Eg it includes the X-RMAIL headers in the yank. Would you ever
> > > want to include the full headers (all the Received: etc) in a reply?
> > 
> > The reason of toggling is just to see the full headers.  I
> > don't intend to yank the full headers when I type r to
> > reply, and type C-c C-y to yank.

> But the original pre-mbox Rmail would always yank the full headers
> when you did that after expanding the headers with
> rmail-toggle-header.

I know.  As I wrote before, I'm using supercite, and with
these customizations:

 '(sc-auto-fill-region-p nil)
 '(sc-citation-delimiter-regexp "[^-][>]+")
 '(sc-citation-leader "")
 '(sc-nested-citation-p t)
 '(sc-preferred-header-style 2)
 '(sc-reference-tag-string "")

all headers are deleted by supercite.

> > I don't mind how the problem is fixed, but with your patch,
> > I get the error "Marker does not point anywhere" when I type
> > C-c C-y.

> Obviously, the bug should be fixed, but please do not kill the feature
> whereby C-c C-y copies the full headers.

I'm not proposing to kill that feature.

---
Kenichi Handa
handa@m17n.org




  reply	other threads:[~2009-02-20 12:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  2:26 rmail-toggle-header problem Kenichi Handa
2009-02-18  5:29 ` Glenn Morris
2009-02-18  6:37   ` Kenichi Handa
2009-02-18 12:10 ` Richard M Stallman
2009-02-19 20:28   ` Glenn Morris
2009-02-20  1:35     ` Kenichi Handa
2009-02-20  2:12       ` Glenn Morris
2009-02-20  8:34         ` Eli Zaretskii
2009-02-20  8:29       ` Eli Zaretskii
2009-02-20 12:59         ` Kenichi Handa [this message]
2009-02-20 13:30     ` Richard M Stallman
2009-02-20 22:21       ` Chetan Pandya
2009-02-21  2:34         ` Stephen J. Turnbull
2009-02-21  1:18       ` Chetan Pandya
2009-02-21  2:21         ` Stefan Monnier
2009-02-21  3:18       ` Glenn Morris
2009-02-21  9:12         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2009-02-20  9:35 Alfred M. Szmidt
2009-02-22  9:25 Xavier Maillard

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LaUy9-0004rx-8d@etlken \
    --to=handa@m17n.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).