From: Justin Burkett <justin@burkett.cc>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Patch for beginning-of-visual-line and end-of-visual-line
Date: Sat, 12 Aug 2017 09:14:47 -0400 [thread overview]
Message-ID: <CAF5dqNJ64TytznqxDA2WR8P-o8_GYLOg47=fBnd6ihotzLeDwQ@mail.gmail.com> (raw)
In-Reply-To: <83wp69htl2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
> The return value is unspecified, and I don't think I see why we should
specify it.
No problem. Thanks again
On Sat, Aug 12, 2017 at 8:13 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Justin Burkett <justin@burkett.cc>
> > Date: Sat, 12 Aug 2017 07:54:16 -0400
> > Cc: emacs-devel@gnu.org
> >
> > So I think this behavior is correct, perhaps we should describe this
> > special case in the doc string. This function must end up at the
> > beginning of a visual line, and in your case there's only one such
> > place. Note that (beginning-of-visual-line 1) and
> > (beginning-of-visual-line) all end up in the same place in this case.
> >
> > That's fine with me. While we're at it, move-beginning-of-line has the
> same inconsistency in the docstring.
>
> I've fixed the doc strings of both these functions, thanks.
>
> > Also, it would be nice to specify what the return value of these
> functions is if the docstring will change.
>
> The return value is unspecified, and I don't think I see why we should
> specify it.
>
[-- Attachment #2: Type: text/html, Size: 1738 bytes --]
next prev parent reply other threads:[~2017-08-12 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 17:24 Patch for beginning-of-visual-line and end-of-visual-line Justin Burkett
2017-08-11 18:41 ` Eli Zaretskii
2017-08-11 21:10 ` Justin Burkett
2017-08-12 6:35 ` Eli Zaretskii
2017-08-12 11:54 ` Justin Burkett
2017-08-12 12:13 ` Eli Zaretskii
2017-08-12 13:14 ` Justin Burkett [this message]
2017-08-12 13:18 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF5dqNJ64TytznqxDA2WR8P-o8_GYLOg47=fBnd6ihotzLeDwQ@mail.gmail.com' \
--to=justin@burkett.cc \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.