mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-15 10:30:25 -08:00
Fix typos.
This commit is contained in:
parent
e65adfac3b
commit
a98edce9ec
19 changed files with 45 additions and 28 deletions
|
|
@ -1,3 +1,7 @@
|
|||
2011-12-06 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* gnus-faq.texi (FAQ 2-1, FAQ 3-8, FAQ 4-14, FAQ 9-1): Fix typos.
|
||||
|
||||
2011-11-24 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* gnus.texi, smtpmail.texi: Fix case of "GnuTLS".
|
||||
|
|
|
|||
|
|
@ -266,9 +266,9 @@ and how to prevent it?
|
|||
@subsubheading Answer
|
||||
|
||||
This message means that the last time you used Gnus, it
|
||||
wasn't properly exited and therefor couldn't write its
|
||||
informations to disk (e.g. which messages you read), you
|
||||
are now asked if you want to restore those informations
|
||||
wasn't properly exited and therefore couldn't write its
|
||||
information to disk (e.g. which messages you read), you
|
||||
are now asked if you want to restore that information
|
||||
from the auto-save file.
|
||||
|
||||
To prevent this message make sure you exit Gnus
|
||||
|
|
@ -563,7 +563,7 @@ However, the first thing to do is to tell Gnus in which way
|
|||
it should store the mail, in Gnus terminology which back end
|
||||
to use. Gnus supports many different back ends, the most
|
||||
commonly used one is nnml. It stores every mail in one file
|
||||
and is therefor quite fast. However you might prefer a one
|
||||
and is therefore quite fast. However you might prefer a one
|
||||
file per group approach if your file system has problems with
|
||||
many small files, the nnfolder back end is then probably the
|
||||
choice for you. To use nnml add the following to ~/.gnus.el:
|
||||
|
|
@ -580,7 +580,7 @@ As you might have guessed, if you want nnfolder, it's
|
|||
@end example
|
||||
@noindent
|
||||
|
||||
Now we need to tell Gnus, where to get it's mail from. If
|
||||
Now we need to tell Gnus, where to get its mail from. If
|
||||
it's a POP3 server, then you need something like this:
|
||||
|
||||
@example
|
||||
|
|
@ -1104,11 +1104,11 @@ I don't like the way the Summary buffer looks, how to tweak it?
|
|||
@subsubheading Answer
|
||||
|
||||
You've got to play around with the variable
|
||||
gnus-summary-line-format. It's value is a string of
|
||||
gnus-summary-line-format. Its value is a string of
|
||||
symbols which stand for things like author, date, subject
|
||||
etc. A list of the available specifiers can be found in the
|
||||
manual node "Summary Buffer Lines" and the often forgotten
|
||||
node "Formatting Variables" and it's sub-nodes. There
|
||||
node "Formatting Variables" and its sub-nodes. There
|
||||
you'll find useful things like positioning the cursor and
|
||||
tabulators which allow you a summary in table form, but
|
||||
sadly hard tabulators are broken in 5.8.8.
|
||||
|
|
@ -2190,7 +2190,7 @@ Starting Gnus is really slow, how to speed it up?
|
|||
|
||||
@subsubheading Answer
|
||||
|
||||
The reason for this could be the way Gnus reads it's
|
||||
The reason for this could be the way Gnus reads its
|
||||
active file, see the node "The Active File" in the Gnus
|
||||
manual for things you might try to speed the process up.
|
||||
An other idea would be to byte compile your ~/.gnus.el (say
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
2011-12-06 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* textmodes/table.el (table-shorten-cell): Fix typo.
|
||||
|
||||
2011-12-05 Christopher Genovese <genovese.cr@gmail.com> (tiny change)
|
||||
|
||||
* emacs-lisp/assoc.el (aput): Fix return value (bug#10146)
|
||||
|
|
|
|||
|
|
@ -6278,7 +6278,7 @@
|
|||
Register changes using allout-exposure-change-hook.
|
||||
Disregard aberrant topics.
|
||||
(allout-shift-in): With universal-argument, make topic a peer of
|
||||
it's former offspring. Simplify the code by separating out
|
||||
its former offspring. Simplify the code by separating out
|
||||
allout-shift-out functionality.
|
||||
(allout-shift-out): With universal-argument, make offspring peers
|
||||
of their former container, and its siblings. Implement the
|
||||
|
|
|
|||
|
|
@ -12129,7 +12129,7 @@
|
|||
|
||||
* cc-mode.el (c-buffer-is-cc-mode):
|
||||
Definition moved here from cc-vars.el. Also,
|
||||
put permanent-local property on variable so it's value won't get
|
||||
put permanent-local property on variable so its value won't get
|
||||
killed by kill-all-local-variables.
|
||||
|
||||
* cc-mode.el (c++-mode, java-mode, objc-mode, idl-mode):
|
||||
|
|
@ -19534,7 +19534,7 @@
|
|||
the innermost test. This catches GNU-style comments.
|
||||
|
||||
* cc-mode.el (c-add-syntax):
|
||||
Move macro definition to before it's first use.
|
||||
Move macro definition to before its first use.
|
||||
|
||||
* cc-mode.el (c-submit-bug-report):
|
||||
Capture buffer local variable values which are
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
2011-12-06 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* semantic/bovine/c.el (semantic-tag-abstract-p): Fix typo.
|
||||
|
||||
2011-11-26 Chong Yidong <cyd@gnu.org>
|
||||
|
||||
* semantic/wisent/python-wy.el:
|
||||
|
|
|
|||
|
|
@ -816,7 +816,7 @@ now.
|
|||
;;
|
||||
;; will create 2 toplevel tags, one is type A, and the other variable B
|
||||
;; where the :type of B is just a type tag A that is a prototype, and
|
||||
;; the actual struct info of A is it's own toplevel tag.
|
||||
;; the actual struct info of A is its own toplevel tag.
|
||||
(when (or (semantic-tag-of-class-p tag 'function)
|
||||
(semantic-tag-of-class-p tag 'variable))
|
||||
(let* ((basetype (semantic-tag-type tag))
|
||||
|
|
@ -1311,7 +1311,7 @@ Optional PARENT and COLOR as specified with
|
|||
"Return non-nil if TAG is considered abstract.
|
||||
PARENT is tag's parent.
|
||||
In C, a method is abstract if it is `virtual', which is already
|
||||
handled. A class is abstract iff it's destructor is virtual."
|
||||
handled. A class is abstract iff its destructor is virtual."
|
||||
(cond
|
||||
((eq (semantic-tag-class tag) 'type)
|
||||
(require 'semantic/find)
|
||||
|
|
|
|||
|
|
@ -2678,7 +2678,7 @@ Anything else means ask for each directory."
|
|||
(defvar dired-re-no-dot "^\\([^.]\\|\\.\\([^.]\\|\\..\\)\\).*")
|
||||
|
||||
;; Delete file, possibly delete a directory and all its files.
|
||||
;; This function is useful outside of dired. One could change it's name
|
||||
;; This function is useful outside of dired. One could change its name
|
||||
;; to e.g. recursive-delete-file and put it somewhere else.
|
||||
(defun dired-delete-file (file &optional recursive trash) "\
|
||||
Delete FILE or directory (possibly recursively if optional RECURSIVE is true.)
|
||||
|
|
|
|||
|
|
@ -2969,7 +2969,7 @@ When FORCE, rebuild the tool bar."
|
|||
'gnus-summary-mode-map)))
|
||||
(when map
|
||||
;; Need to set `gnus-summary-tool-bar-map' because `gnus-article-mode'
|
||||
;; uses it's value.
|
||||
;; uses its value.
|
||||
(setq gnus-summary-tool-bar-map map))))
|
||||
(set (make-local-variable 'tool-bar-map) gnus-summary-tool-bar-map))
|
||||
|
||||
|
|
|
|||
|
|
@ -428,7 +428,7 @@
|
|||
2004-11-08 Satyaki Das <satyaki@theforce.stanford.edu>
|
||||
|
||||
* mh-acros.el (mh-funcall-if-exists): In XEmacs, presence of a
|
||||
function at compile time doesn't guarantee it's existence at run
|
||||
function at compile time doesn't guarantee its existence at run
|
||||
time. So make the macro handle that situation better.
|
||||
|
||||
2004-11-05 Satyaki Das <satyaki@theforce.stanford.edu>
|
||||
|
|
@ -10195,7 +10195,7 @@
|
|||
2002-04-02 Peter S Galbraith <psg@debian.org>
|
||||
|
||||
* mh-e.el: 'defvar mh-folder-unseen-seq-name' called a function to
|
||||
set it's value, and this happens also on byte-compilation (where
|
||||
set its value, and this happens also on byte-compilation (where
|
||||
it can fail if the user's MH environment is not setup correctly).
|
||||
I now set the value of mh-folder-unseen-seq-name at runtime when I
|
||||
first need it. This should fix Debian bugs
|
||||
|
|
|
|||
|
|
@ -1,3 +1,8 @@
|
|||
2011-12-06 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* ob.el (org-babel-expand-body:generic, org-babel-number-p):
|
||||
* ob-ref.el (org-babel-ref-parse): Fix typos.
|
||||
|
||||
2011-11-24 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* ob.el (org-babel-execute-src-block): Fix typo.
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
"Parse a variable ASSIGNMENT in a header argument.
|
||||
If the right hand side of the assignment has a literal value
|
||||
return that value, otherwise interpret as a reference to an
|
||||
external resource and find it's value using
|
||||
external resource and find its value using
|
||||
`org-babel-ref-resolve'. Return a list with two elements. The
|
||||
first element of the list will be the name of the variable, and
|
||||
the second will be an emacs-lisp representation of the value of
|
||||
|
|
|
|||
|
|
@ -464,7 +464,7 @@ block."
|
|||
|
||||
(defun org-babel-expand-body:generic (body params &optional var-lines)
|
||||
"Expand BODY with PARAMS.
|
||||
Expand a block of code with org-babel according to it's header
|
||||
Expand a block of code with org-babel according to its header
|
||||
arguments. This generic implementation of body expansion is
|
||||
called for languages which have not defined their own specific
|
||||
org-babel-expand-body:lang function."
|
||||
|
|
@ -2045,7 +2045,7 @@ appropriate."
|
|||
cell))
|
||||
|
||||
(defun org-babel-number-p (string)
|
||||
"If STRING represents a number return it's value."
|
||||
"If STRING represents a number return its value."
|
||||
(if (and (string-match "^-?[0-9]*\\.?[0-9]*$" string)
|
||||
(= (length (substring string (match-beginning 0)
|
||||
(match-end 0)))
|
||||
|
|
|
|||
|
|
@ -715,7 +715,7 @@ If :auto-sitemap is set, publish the sitemap too.
|
|||
If :makeindex is set, also produce a file theindex.org."
|
||||
(mapc
|
||||
(lambda (project)
|
||||
;; Each project uses it's own cache file:
|
||||
;; Each project uses its own cache file:
|
||||
(org-publish-initialize-cache (car project))
|
||||
(let*
|
||||
((project-plist (cdr project))
|
||||
|
|
|
|||
|
|
@ -586,7 +586,7 @@ in a mode hook, you have to call `c-setup-doc-comment-style'
|
|||
afterwards to redo that work."
|
||||
;; Symbols other than those documented above may be used on this
|
||||
;; variable. If a variable exists that has that name with
|
||||
;; "-font-lock-keywords" appended, it's value is prepended to the
|
||||
;; "-font-lock-keywords" appended, its value is prepended to the
|
||||
;; font lock keywords list. If it's a function then it's called and
|
||||
;; the result is prepended.
|
||||
:type '(radio
|
||||
|
|
|
|||
|
|
@ -345,7 +345,7 @@
|
|||
;; Above code is well known ~/.emacs idiom for customizing a mode
|
||||
;; specific keymap however it does not work for this package. This is
|
||||
;; because there is no table mode in effect. This package does not
|
||||
;; use a local map therefor you must modify `table-cell-map'
|
||||
;; use a local map therefore you must modify `table-cell-map'
|
||||
;; explicitly. The correct way of achieving above task is:
|
||||
;;
|
||||
;; (add-hook 'table-cell-map-hook
|
||||
|
|
@ -2155,7 +2155,7 @@ specified."
|
|||
(defun table-shorten-cell (n)
|
||||
"Shorten the current cell by N lines by shrinking the cell vertically.
|
||||
Shortening is done by removing blank lines from the bottom of the cell
|
||||
and possibly from the top of the cell as well. Therefor, the cell
|
||||
and possibly from the top of the cell as well. Therefore, the cell
|
||||
must have some bottom/top blank lines to be shorten effectively. This
|
||||
is applicable to all the cells aligned horizontally with the current
|
||||
one because they are also shortened in order to keep the rectangular
|
||||
|
|
|
|||
|
|
@ -2448,7 +2448,7 @@
|
|||
* lisp/url-nfs.el (url-nfs-create-wrapper): New function to create
|
||||
wrappers onto the appropriate file-based URLs for file-name-handlers.
|
||||
|
||||
* lisp/url-ftp.el: Moved the FTP stuff into it's own file - it
|
||||
* lisp/url-ftp.el: Moved the FTP stuff into its own file - it
|
||||
might get messy with file-name-handlers and things.
|
||||
|
||||
* lisp/url-http.el (url-http-clean-headers): Fix problem when
|
||||
|
|
|
|||
|
|
@ -839,7 +839,7 @@ do_symval_forwarding (register union Lisp_Fwd *valcontents)
|
|||
|
||||
case Lisp_Fwd_Kboard_Obj:
|
||||
/* We used to simply use current_kboard here, but from Lisp
|
||||
code, it's value is often unexpected. It seems nicer to
|
||||
code, its value is often unexpected. It seems nicer to
|
||||
allow constructions like this to work as intuitively expected:
|
||||
|
||||
(with-selected-frame frame
|
||||
|
|
|
|||
|
|
@ -705,7 +705,7 @@ struct font_driver
|
|||
|
||||
|
||||
/* Chain of font drivers. There's one global font driver list
|
||||
(font_driver_list in font.c). In addition, each frame has it's own
|
||||
(font_driver_list in font.c). In addition, each frame has its own
|
||||
font driver list at FRAME_PTR->font_driver_list. */
|
||||
|
||||
struct font_driver_list
|
||||
|
|
@ -721,7 +721,7 @@ struct font_driver_list
|
|||
|
||||
|
||||
/* Chain of arbitrary data specific to each font driver. Each frame
|
||||
has it's own font data list at FRAME_PTR->font_data_list. */
|
||||
has its own font data list at FRAME_PTR->font_data_list. */
|
||||
|
||||
struct font_data_list
|
||||
{
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue