From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: informat.el: `Info-split' split size
Date: Thu, 25 Sep 2008 06:10:58 +0300 [thread overview]
Message-ID: <uod2cly2l.fsf@gnu.org> (raw)
In-Reply-To: <b4mljxhdrld.fsf@jpl.org>
> Date: Thu, 25 Sep 2008 08:58:06 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: ding@gnus.org
>
> > ,----[ <f1> f Info-split RET ]
> >| Info-split is an interactive autoloaded Lisp function in `informat'.
> >| (Info-split)
> >|
> >| Split an info file into an indirect file plus bounded-size subfiles.
> >| Each subfile will be up to 50,000 characters plus one node. [...]
> > `----
>
> > I think the threshold should not be hard-coded and it's default should
> > be like makeinfo's so that we don't need such workarounds:
>
> >> A workaround I added to the Japanese edition of the Gnus Info is:
> [...]
> >> (require 'informat)
> >> (let* ((fn (symbol-function 'Info-split))
> >> (fns (prin1-to-string fn)))
> >> (when (string-match "\\([\t\n ]+\\)50000\\([\t\n ]+\\)" fns)
> >> (condition-case nil
> >> (fset 'Info-split (read (replace-match "\\1200000\\2" nil nil fns)))
> >> (error
> >> (fset 'Info-split fn)))))
>
> Thank you for following it up. How about the attached patch?
> While the threshold of makeinfo is 30000, I tried it with some
^^^^^
You mean 300000, right?
next prev parent reply other threads:[~2008-09-25 3:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87abfkmuko.fsf@jondo.cante.net>
2008-08-13 8:29 ` Group, Summary buffers: End of line contain whitespaces Katsumi Yamaoka
2008-08-13 18:56 ` Reiner Steib
2008-08-13 21:47 ` Jari Aalto
2008-08-15 16:31 ` jidanni
2008-08-19 11:48 ` Miles Bader
2008-08-22 15:52 ` Ted Zlatanov
2008-08-27 23:01 ` Miles Bader
2008-08-28 13:51 ` Ted Zlatanov
2008-08-29 11:15 ` Reiner Steib
2008-08-29 15:12 ` bugs and features (was: Group, Summary buffers: End of line contain whitespaces) Ted Zlatanov
2008-09-15 21:00 ` registry doc patch (was: bugs and features) Ted Zlatanov
2008-09-16 9:17 ` registry doc patch Rupert Swarbrick
2008-09-16 13:36 ` Ted Zlatanov
2008-09-16 12:30 ` Magnus Henoch
2008-09-16 13:39 ` Ted Zlatanov
2008-09-18 23:19 ` Katsumi Yamaoka
2008-09-19 16:19 ` Ted Zlatanov
2008-09-23 19:18 ` Reiner Steib
2008-09-24 0:37 ` Katsumi Yamaoka
2008-09-24 6:45 ` Katsumi Yamaoka
2008-09-24 16:45 ` Reiner Steib
2008-09-24 16:44 ` informat.el: `Info-split' split size (was: registry doc patch) Reiner Steib
2008-09-24 23:58 ` informat.el: `Info-split' split size Katsumi Yamaoka
2008-09-25 3:10 ` Eli Zaretskii [this message]
2008-09-25 4:01 ` Katsumi Yamaoka
2008-09-25 23:10 ` Katsumi Yamaoka
2008-08-29 13:51 ` Group, Summary buffers: End of line contain whitespaces Ted Zlatanov
2008-08-29 15:31 ` Daiki Ueno
2008-08-29 15:55 ` Ted Zlatanov
2008-08-30 5:07 ` Katsumi Yamaoka
2008-08-30 9:33 ` Ted Zlatanov
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=uod2cly2l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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).