From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ding@ifi.uio.no
Subject: Re: [nntp.el] patch for the unofficial version of mule based on 19.30
Date: Fri, 29 Dec 1995 15:13:28 +0100 [thread overview]
Message-ID: <199512291413.PAA20542@durin.uio.no> (raw)
In-Reply-To: <10696.819717489@deneb.is.s.u-tokyo.ac.jp>
> If you are using the current version of September Gnus on the
> unofficial version of mule based on 19.29 or 19.30 and not using tm
> package, your posting messages to the news would be damaged.
> (...)
> Of course, this code will be slower than the original.
> (...)
> ! (setq last (save-excursion
> ! (goto-char (min (+ last size) (point-max)))
> ! (or (eobp) (forward-char 1))
> ! (point))))
How is this different from:
(setq last (save-excursion
(goto-char (+ last size 1))
(point))))
(since goto-char always stays between point-min and point-max), or just
(setq last (min (+ last size 1) (point-max))))
? Except if the result can somehow become smaller than (point-min).
Then you need
(setq last (max (min (+ last size 1) (point-max)) (point-min))))
Regards,
Hallvard
prev parent reply other threads:[~1995-12-29 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-23 11:18 SAKIYAMA Nobuo
1995-12-29 14:13 ` Hallvard B Furuseth [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=199512291413.PAA20542@durin.uio.no \
--to=h.b.furuseth@usit.uio.no \
--cc=ding@ifi.uio.no \
/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).