Mercurial > hg > xemacs-beta
view man/lispref/index.texi @ 5914:bd4d2c8ef9cc
Use the existing C-level line number cache within #'line-number.
src/ChangeLog addition:
2015-05-15 Aidan Kehoe <kehoea@parhasard.net>
* buffer.c:
* buffer.c (Fline_number): New C implementation, using the line
number cache of line-number.c, with a new optional BUFFER
argument.
* buffer.c (syms_of_buffer):
Make it available to Lisp.
* line-number.c (buffer_line_number):
New argument, RESPECT-NARROWING, describing whether to count from
the beginning of the visible region or from the beginning of the
buffer.
* line-number.h:
* line-number.h (buffer_line_number): Update its declaration.
* redisplay.c (window_line_number): Call it with the new argument.
lisp/ChangeLog addition:
2015-05-15 Aidan Kehoe <kehoea@parhasard.net>
* simple.el:
* simple.el (line-number): Moved to buffer.c; we have an existing
line number cache in C, it's a shame not to have it available.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Fri, 15 May 2015 18:11:47 +0100 |
parents | 576fb035e263 |
children |
line wrap: on
line source
@c -*-texinfo-*- @setfilename ../../info/index.info @c Indexing guidelines @c I assume that all indexes will be combined. @c Therefore, if a generated findex and permutations @c cover the ways an index user would look up the entry, @c then no cindex is added. @c Concept index (cindex) entries will also be permuted. Therefore, they @c have no commas and few irrelevant connectives in them. @c I tried to include words in a cindex that give the context of the entry, @c particularly if there is more than one entry for the same concept. @c For example, "nil in keymap" @c Similarly for explicit findex and vindex entries, e.g. "print example". @c Error codes are given cindex entries, e.g. "end-of-file error". @c pindex is used for .el files and Unix programs @node Index, , Standard Hooks, Top @unnumbered Index @ignore All variables, functions, keys, programs, files, and concepts are in this one index. All names and concepts are permuted, so they appear several times, one for each permutation of the parts of the name. For example, @code{function-name} would appear as @b{function-name} and @b{name, function-}. Key entries are not permuted, however. @end ignore @c Print the indices @printindex fn