From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 29373-done@debbugs.gnu.org
Subject: bug#29373: 24.5; doc string of `self-insert-uses-region-functions'
Date: Fri, 24 Nov 2017 08:43:05 -0800 (PST) [thread overview]
Message-ID: <86584c33-6e52-4cf5-8e22-bb9952b296b2@default> (raw)
In-Reply-To: <<83h8tk9chp.fsf@gnu.org>>
> -----Original Message-----
> From: Eli Zaretskii [mailto:eliz@gnu.org]
> Sent: Friday, November 24, 2017 2:51 AM
> To: Drew Adams <drew.adams@oracle.com>
> Cc: 29373-done@debbugs.gnu.org
> Subject: Re: bug#29373: 24.5; doc string of `self-insert-uses-region-
> functions'
>
> > Date: Mon, 20 Nov 2017 18:56:15 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> >
> > Two lines of the doc string are too long.
>
> Longer than 79 characters? I didn't find any such lines.
Where do you see 79 as the recommended max length?
Traditionaly it has been 70, IIRC.
From (elisp) `Documentation Tips':
Format the documentation string so that it fits in an Emacs window
on an 80-column screen. It is a good idea for most lines to be no
wider than 60 characters. The first line should not be wider than
67 characters or it will look bad in the output of 'apropos'.
https://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
1 out of the 5 lines is less than 61 chars - not most.
But if you're happy with the lengths as is, fine.
> > The doc string is close to incomprehensible.
>
> Such derogatory remarks are best kept out of bug reports. The facts
> are grave enough to tell we should fix this.
Nothing derogatory intended. That's a summary of the
problem - lack of clarity overall. For me, at least,
the wording of this doc is not very understandable.
I have no idea who wrote it, nor do I care. It's not
about blaming or attacking anyone. It's about calling
your attention to what I, at least, think is a doc
string that needs some love (improvement). And the
overall problem is not the technical content; it is
the lack of clarity - comprehensibility. To me, at
least.
Anyway, I'm sure you made an improvement, whatever
change you made. Thanks for that.
next parent reply other threads:[~2017-11-24 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d8b52361-9340-4a18-b2fd-557c78c382d7@default>
[not found] ` <<83h8tk9chp.fsf@gnu.org>
2017-11-24 16:43 ` Drew Adams [this message]
2017-11-24 17:07 ` bug#29373: 24.5; doc string of `self-insert-uses-region-functions' Eli Zaretskii
[not found] <<<d8b52361-9340-4a18-b2fd-557c78c382d7@default>
[not found] ` <<<83h8tk9chp.fsf@gnu.org>
[not found] ` <<86584c33-6e52-4cf5-8e22-bb9952b296b2@default>
[not found] ` <<83y3mv8v1r.fsf@gnu.org>
2017-11-24 17:33 ` Drew Adams
2017-11-25 23:56 ` Noam Postavsky
2017-11-21 2:56 Drew Adams
2017-11-24 10:50 ` 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
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=86584c33-6e52-4cf5-8e22-bb9952b296b2@default \
--to=drew.adams@oracle.com \
--cc=29373-done@debbugs.gnu.org \
--cc=eliz@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 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).