From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: [PATCH] message-goto-body after <#secure
Date: Thu, 25 Nov 2010 00:19:20 +0100 [thread overview]
Message-ID: <m3wro25myv.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87pqtu5n3x.fsf@kotik.lan>
Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
> I give up (but I still would like C-c C-b to beam me up to the right
> point)
But what the right point is depends on what you're doing. If, for
instance, you have a multipart/alternative message, you may want it to
go to the beginning of the first part. Or not. Or you may want it to
go to after the "writes:" line. So you should just bind `C-c C-b' to go
to where you want it to go...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-11-24 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 20:55 Łukasz Stelmach
2010-11-24 17:28 ` Julien Danjou
2010-11-24 20:53 ` Lars Magne Ingebrigtsen
2010-11-24 21:20 ` Julien Danjou
2010-11-24 23:16 ` Łukasz Stelmach
2010-11-24 23:19 ` Lars Magne Ingebrigtsen [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=m3wro25myv.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).