From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Some MIME suggestions...
Date: 18 Oct 1998 19:28:37 +0200 [thread overview]
Message-ID: <kigu31193ui.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "18 Oct 1998 18:23:39 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > > Er... Yes, one really should. But that kinda makes all the
> > > highlighting and everything away, which makes things a bit
> > > awkward.
> >
> > Why would that make it awkward? Aren't highlights *supposed* to go
> > away when you're editing the article?
>
> I don't really see why.
You have a point.
However, the point stands (IMHO) only as long as we're talking about
highlighting, as opposed to changing the text. And many currenn
display hooks do change the text, e.g. `W w'. Somehow I think that
`e' should always present the original article, the same stuff you get
with `C-u g'.
> It's also an efficiency thing -- re-highlighting everything after
> every little edit would be annoying, especially in large articles.
Are people really editing stuff that often to make this a problem?
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Psychos _do not_ explode when sunlight hits them."
next prev parent reply other threads:[~1998-10-18 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-13 20:47 Hrvoje Niksic
1998-10-14 4:22 ` Shenghuo ZHU
1998-10-14 8:25 ` Hrvoje Niksic
1998-10-14 8:55 ` Steinar Bang
1998-10-14 9:06 ` Hrvoje Niksic
1998-10-14 6:35 ` Steinar Bang
1998-10-17 20:54 ` Lars Magne Ingebrigtsen
1998-10-18 12:56 ` Hrvoje Niksic
1998-10-18 16:23 ` Lars Magne Ingebrigtsen
1998-10-18 17:28 ` Hrvoje Niksic [this message]
1998-10-18 22:26 ` Lars Magne Ingebrigtsen
1998-10-19 18:35 ` Paul Franklin
1998-10-19 19:33 ` Lars Magne Ingebrigtsen
1998-10-20 8:34 ` Hrvoje Niksic
1998-10-19 19:44 ` Kai Grossjohann
1998-10-19 19:40 ` Kai Grossjohann
1998-10-19 20:11 ` 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=kigu31193ui.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).