From: Simon Josefsson <jas@extundo.com>
Subject: Re: gnus-url-mailto broken on foo+bar@somewhere.invalid
Date: Fri, 05 Sep 2003 00:42:32 +0200 [thread overview]
Message-ID: <iluu17syy3r.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3ptigih4k.fsf@defun.localdomain> (Jesper Harder's message of "Thu, 04 Sep 2003 19:43:39 +0200")
Jesper Harder <harder@myrealbox.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> I actually use them sometime, because they have a reload button, which
>> is handy if you are writing documentation. C-h i C-x k RET C-u C-h i
>> /file/to/manual RET and then finding the spot you are working on is
>> harder then clicking on reload.
>>
>> Hm. Perhaps info has this feature too, but I haven't found it and I
>> looked for 'reload', 'reread' etc. But I'd bet that if there is a key
>> binding, I will learn it soon, thanks to this list. :)
>
> `C-c RET C-b' (`makeinfo-buffer') is really nifty. It runs makeinfo,
> opens the resulting info file, and jumps to the node where point was
> in the texinfo file.
Ah, that looks useful, thanks! Thanks also to Reiner.
next prev parent reply other threads:[~2003-09-04 22:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 16:52 Reiner Steib
2003-08-26 18:05 ` Karl Pflästerer
2003-08-27 13:22 ` Reiner Steib
2003-08-27 14:43 ` Karl Pflästerer
2003-08-26 21:37 ` Jesper Harder
2003-08-27 11:42 ` Benjamin Riefenstahl
2003-08-27 13:57 ` Reiner Steib
2003-08-27 14:53 ` Jesper Harder
2003-08-27 17:37 ` Kai Großjohann
2003-08-27 18:33 ` Jesper Harder
2003-09-04 1:59 ` Jesper Harder
2003-09-04 13:15 ` Reiner Steib
2003-09-04 15:32 ` Jesper Harder
2003-09-04 16:10 ` Simon Josefsson
2003-09-04 16:53 ` Reloading info files (was: gnus-url-mailto broken on foo+bar@somewhere.invalid) Reiner Steib
2003-09-05 21:58 ` Reloading info files Kevin Ryde
2003-09-04 17:43 ` gnus-url-mailto broken on foo+bar@somewhere.invalid Jesper Harder
2003-09-04 22:42 ` Simon Josefsson [this message]
2003-09-04 21:46 ` Frank Schmitt
2003-09-05 1:34 ` Jesper Harder
2003-09-05 7:33 ` Frank Schmitt
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=iluu17syy3r.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).