unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Markus Triska <markus.triska@gmx.at>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>,
	rms@gnu.org, drew.adams@oracle.com, miles@gnu.org
Subject: Re: cannot understand Elisp manual node Glyphs
Date: Fri, 09 Feb 2007 10:12:54 +0100	[thread overview]
Message-ID: <87sldfzobt.fsf@gmx.at> (raw)
In-Reply-To: <86ejozhkae.fsf@lola.quinscape.zz> (David Kastrup's message of "Fri\, 09 Feb 2007 08\:17\:29 +0100")

David Kastrup <dak@gnu.org> writes:

> one.  Anyway, it is getting increasingly hard for developers to
> maintain sight of _what_ it is the time to do.

It's time to look harder.


2007-02-09  Markus Triska  <markus.triska@gmx.at>

	* cmds.c (Fforward_line, Fbackward_char, Fforward_char): Document
	behaviour for omitted optional arguments

*** cmds.c	21 Jan 2007 05:18:16 +0100	1.99
--- cmds.c	09 Feb 2007 10:03:12 +0100	
***************
*** 57,63 ****
  
  DEFUN ("forward-char", Fforward_char, Sforward_char, 0, 1, "p",
         doc: /* Move point right N characters (left if N is negative).
! On reaching end of buffer, stop and signal error.  */)
       (n)
       Lisp_Object n;
  {
--- 57,64 ----
  
  DEFUN ("forward-char", Fforward_char, Sforward_char, 0, 1, "p",
         doc: /* Move point right N characters (left if N is negative).
! On reaching end of buffer, stop and signal error.  N nil or omitted is
! equivalent to N = 1.  */)
       (n)
       Lisp_Object n;
  {
***************
*** 93,99 ****
  
  DEFUN ("backward-char", Fbackward_char, Sbackward_char, 0, 1, "p",
         doc: /* Move point left N characters (right if N is negative).
! On attempt to pass beginning or end of buffer, stop and signal error.  */)
       (n)
       Lisp_Object n;
  {
--- 94,101 ----
  
  DEFUN ("backward-char", Fbackward_char, Sbackward_char, 0, 1, "p",
         doc: /* Move point left N characters (right if N is negative).
! On attempt to pass beginning or end of buffer, stop and signal error.
! N nil or omitted is equivalent to N = 1.  */)
       (n)
       Lisp_Object n;
  {
***************
*** 113,119 ****
  Returns the count of lines left to move.  If moving forward,
  that is N - number of lines moved; if backward, N + number moved.
  With positive N, a non-empty line at the end counts as one line
!   successfully moved (for the return value).  */)
       (n)
       Lisp_Object n;
  {
--- 115,122 ----
  Returns the count of lines left to move.  If moving forward,
  that is N - number of lines moved; if backward, N + number moved.
  With positive N, a non-empty line at the end counts as one line
! successfully moved (for the return value).  N nil or omitted is
! equivalent to N = 1.  */)
       (n)
       Lisp_Object n;
  {

  reply	other threads:[~2007-02-09  9:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 23:11 cannot understand Elisp manual node Glyphs Drew Adams
2007-02-07 13:29 ` Kim F. Storm
2007-02-07 14:54   ` Drew Adams
2007-02-07 15:24     ` Kim F. Storm
2007-02-07 15:53       ` Drew Adams
2007-02-07 16:16         ` Stuart D. Herring
2007-02-07 16:21           ` Drew Adams
2007-02-08 16:38             ` Stuart D. Herring
2007-02-07 22:52   ` Miles Bader
2007-02-08  8:26     ` Kim F. Storm
2007-02-08  8:51       ` David Kastrup
2007-02-08 10:39         ` Kim F. Storm
2007-02-08 23:46           ` Richard Stallman
2007-02-09  7:17             ` David Kastrup
2007-02-09  9:12               ` Markus Triska [this message]
2007-02-09  9:43                 ` Nick Roberts
2007-02-09 23:48                 ` Richard Stallman
2007-02-09 14:23               ` Richard Stallman
2007-02-09 11:12             ` Kim F. Storm
2007-02-09 11:32               ` Juanma Barranquero
2007-02-09 23:48                 ` Richard Stallman
2007-02-09 14:05               ` Kim F. Storm
2007-02-09 23:49                 ` Richard Stallman
2007-02-10  0:40                   ` Drew Adams
2007-02-10 17:40                     ` Richard Stallman
2007-02-11 14:18                       ` Miles Bader
2007-02-11 21:07                       ` Kim F. Storm
2007-02-12 17:53                         ` Richard Stallman
2007-02-14 23:32                           ` Kim F. Storm
2007-02-10 10:19                   ` Eli Zaretskii
2007-02-10 17:41                     ` Richard Stallman
2007-02-10 13:59                   ` Miles Bader
2007-02-11  0:20                     ` Richard Stallman
2007-02-11  1:34                       ` Drew Adams
2007-02-11 14:16                       ` Miles Bader
2007-02-12 17:52                         ` Richard Stallman
2007-02-09 18:16               ` Stuart D. Herring
2007-02-08 16:21       ` Stefan Monnier
2007-02-08 16:36         ` Juanma Barranquero
2007-02-08  9:58     ` Stephen J. Turnbull

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sldfzobt.fsf@gmx.at \
    --to=markus.triska@gmx.at \
    --cc=dak@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).