GNU bug report logs - #14843
24.3.50; `line-move', `line-move-visual' need doc strings

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 14843 <at> debbugs.gnu.org
Subject: bug#14843: 24.3.50; `line-move', `line-move-visual' need doc strings
Date: Thu, 11 Jul 2013 22:06:41 +0300

> Date: Thu, 11 Jul 2013 11:50:06 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: 14843 <at> debbugs.gnu.org
> 
> > > These functions, especially `line-move', are used all over the place.
> > > They need doc strings, with complete descriptions of their parameters.
> > 
> > They are internal functions.  Under what circumstances did you need to
> > use them directly?  Why wasn't next/previous-line enough?
> 
> Read what I wrote: they "are used all over the place".  In the Emacs code
> alone, not to mention in 3rd-party code.  They are not "internal" to
> simple.el.  They are not internal to anything.  Reality.

That an internal function is used all over the Emacs code is a small
wonder.  It just means someone was smart enough to capture a frequent
need of many features.

As for 3rd-party code, if you have such code, or happen to know why
line-move was used instead of next/previous-line, please tell.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.