org.texi: Delete trailing whitespaces.
This commit is contained in:
parent
e375cfd834
commit
66cc45e670
16
doc/org.texi
16
doc/org.texi
|
@ -2667,13 +2667,13 @@ and use them in formula syntax for Calc.
|
|||
@cindex Lisp forms, as table formulas
|
||||
|
||||
It is also possible to write a formula in Emacs Lisp. This can be useful
|
||||
for string manipulation and control structures, if Calc's functionality is
|
||||
not enough.
|
||||
for string manipulation and control structures, if Calc's functionality is
|
||||
not enough.
|
||||
|
||||
If a formula starts with a single-quote followed by an opening parenthesis,
|
||||
then it is evaluated as a Lisp form. The evaluation should return either a
|
||||
string or a number. Just as with @file{calc} formulas, you can specify modes
|
||||
and a printf format after a semicolon.
|
||||
and a printf format after a semicolon.
|
||||
|
||||
With Emacs Lisp forms, you need to be conscious about the way field
|
||||
references are interpolated into the form. By default, a reference will be
|
||||
|
@ -2828,7 +2828,7 @@ will apply it to that many consecutive fields in the current column.
|
|||
@cindex lookup functions in tables
|
||||
@cindex table lookup functions
|
||||
|
||||
Org has three predefined Emacs Lisp functions for lookups in tables.
|
||||
Org has three predefined Emacs Lisp functions for lookups in tables.
|
||||
@table @code
|
||||
@item (org-lookup-first VAL S-LIST R-LIST &optional PREDICATE)
|
||||
@findex org-lookup-first
|
||||
|
@ -2846,14 +2846,14 @@ is returned.
|
|||
@item (org-lookup-last VAL S-LIST R-LIST &optional PREDICATE)
|
||||
@findex org-lookup-last
|
||||
Similar to @code{org-lookup-first} above, but searches for the @i{last}
|
||||
element for which @code{PREDICATE} is @code{t}.
|
||||
element for which @code{PREDICATE} is @code{t}.
|
||||
@item (org-lookup-all VAL S-LIST R-LIST &optional PREDICATE)
|
||||
@findex org-lookup-all
|
||||
Similar to @code{org-lookup-first}, but searches for @i{all} elements for
|
||||
which @code{PREDICATE} is @code{t}, and returns @i{all} corresponding
|
||||
values. This function can not be used by itself in a formula, because it
|
||||
returns a list of values. However, powerful lookups can be built when this
|
||||
function is combined with other Emacs Lisp functions.
|
||||
function is combined with other Emacs Lisp functions.
|
||||
@end table
|
||||
|
||||
If the ranges used in these functions contain empty fields, the @code{E} mode
|
||||
|
@ -6156,7 +6156,7 @@ is only necessary if you edit the timestamps directly. If you change
|
|||
them with @kbd{S-@key{cursor}} keys, the update is automatic.
|
||||
@orgcmd{C-S-@key{up/down},org-clock-timestamps-up/down}
|
||||
On @code{CLOCK} log lines, increase/decrease both timestamps so that the
|
||||
clock duration keeps the same.
|
||||
clock duration keeps the same.
|
||||
@orgcmd{S-M-@key{up/down},org-timestamp-up/down}
|
||||
On @code{CLOCK} log lines, increase/decrease the timestamp at point and
|
||||
the one of the previous (or the next clock) timestamp by the same duration.
|
||||
|
@ -16616,7 +16616,7 @@ rely on outline paths, in the hope that these will be unique enough.}.
|
|||
Finally, Org writes the file @file{index.org}, containing links to all other
|
||||
files. @i{MobileOrg} first reads this file from the server, and then
|
||||
downloads all agendas and Org files listed in it. To speed up the download,
|
||||
MobileOrg will only read files whose checksums@footnote{Checksums are stored
|
||||
MobileOrg will only read files whose checksums@footnote{Checksums are stored
|
||||
automatically in the file @file{checksums.dat}} have changed.
|
||||
|
||||
@node Pulling from MobileOrg, , Pushing to MobileOrg, MobileOrg
|
||||
|
|
Loading…
Reference in New Issue