From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Numbering invisible parts
Date: 31 Oct 1999 23:22:02 -0500 [thread overview]
Message-ID: <2nso2qaljp.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Hrvoje Niksic's message of "01 Nov 1999 04:43:47 +0100"
>>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:
[...]
Hrvoje> One things that bothers me about `K b' is that it's very slow.
Hrvoje> It would be really nice if it merely inserted the buttons. As
Hrvoje> it is, it probably re-parses the message (I haven't checked.)
Right.
Unfortunately, a handle is unaware where to insert its button
(beginning marker is unknown to the handle).
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-11-01 4:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-31 23:32 Hrvoje Niksic
1999-11-01 0:23 ` Kai Großjohann
1999-11-01 0:36 ` Hrvoje Niksic
1999-11-01 2:50 ` Shenghuo ZHU
1999-11-01 2:57 ` Hrvoje Niksic
1999-11-01 3:42 ` Shenghuo ZHU
1999-11-01 3:54 ` Hrvoje Niksic
1999-11-01 12:47 ` Steinar Bang
1999-11-01 3:39 ` David S. Goldberg
1999-11-01 3:43 ` Hrvoje Niksic
1999-11-01 4:22 ` Shenghuo ZHU [this message]
1999-11-07 0:34 ` Lars Magne Ingebrigtsen
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=2nso2qaljp.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).