From: Katsumi Yamaoka <yamaoka@jpl.org>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: informat.el: `Info-split' split size
Date: Thu, 25 Sep 2008 08:58:06 +0900 [thread overview]
Message-ID: <b4mljxhdrld.fsf@jpl.org> (raw)
In-Reply-To: <87r679qysj.fsf_-_@marauder.physik.uni-ulm.de>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
>>>>> Reiner Steib wrote:
> On Wed, Sep 24 2008, Katsumi Yamaoka wrote:
>> BTW, with MAKEINFO=no the Gnus Info files are divided into 24
>> files (gnus, gnus-1, ..., gnus-23). Those are too small, aren't
>> they? The threshold is hard-coded in `Info-split' (informat.el).
> ,----[ <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
texinfo files and reduced it a bit for `Info-split'. Now the
command ``./configure; make MAKEINFO=no info'' performed in the
Gnus trunk splits the Gnus Info into six files.
(Note that loaddefs.el, i.e. ldefs-boot.el, should be updated if
this patch is applied because of autoloading `Info-split-threshold'.)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-diff, Size: 1732 bytes --]
--- informat.el~ 2008-05-06 07:57:40 +0000
+++ informat.el 2008-09-24 23:54:45 +0000
@@ -153,9 +153,16 @@
\f
;;;###autoload
+(defcustom Info-split-threshold 262144
+ "The number of characters by which `Info-split' splits an info file."
+ :type 'integer
+ :group 'texinfo)
+
+;;;###autoload
(defun 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.
+Each subfile will be up to the number of characters that
+`Info-split-threshold' specifies, plus one node.
To use this command, first visit a large Info file that has a tag
table. The buffer is modified into a (small) indirect info file which
@@ -167,7 +174,7 @@
contains just the tag table and a directory of subfiles."
(interactive)
- (if (< (buffer-size) 70000)
+ (if (< (buffer-size) (+ 20000 Info-split-threshold))
(error "This is too small to be worth splitting"))
(goto-char (point-min))
(search-forward "\^_")
@@ -192,7 +199,7 @@
(narrow-to-region (point-min) (point))
(goto-char (point-min))
(while (< (1+ (point)) (point-max))
- (goto-char (min (+ (point) 50000) (point-max)))
+ (goto-char (min (+ (point) Info-split-threshold) (point-max)))
(search-forward "\^_" nil 'move)
(setq subfiles
(cons (list (+ start chars-deleted)
--- textmodes/texinfmt.el~ 2008-07-31 21:47:43 +0000
+++ textmodes/texinfmt.el 2008-09-24 23:54:45 +0000
@@ -166,7 +166,7 @@
(Info-tagify)
(if nosplit
nil
- (if (> (buffer-size) 100000)
+ (if (> (buffer-size) (+ 50000 Info-split-threshold))
(progn
(message (setq lastmessage "Splitting Info file..."))
(Info-split))))
next prev parent reply other threads:[~2008-09-24 23:58 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 ` Katsumi Yamaoka [this message]
2008-09-25 3:10 ` informat.el: `Info-split' split size Eli Zaretskii
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=b4mljxhdrld.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).