From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: spinuvit@gmail.com, andreas.roehler@online.de, emacs-devel@gnu.org
Subject: RE: [Emacs-diffs] widen-limits c331b66: Implement buffer-widen-limits functionality
Date: Thu, 24 Mar 2016 07:41:50 -0700 (PDT) [thread overview]
Message-ID: <9307373f-0ecd-4825-8b9c-20280b9c92c0@default> (raw)
In-Reply-To: <<838u1835si.fsf@gnu.org>>
> > And the text about indentation and the use of sub-mode for only a given
> > chunk of text in a buffer is incomprehensible without some explanation.
> > Normally, a major mode, no matter whether it is derived from some other
> > major mode, has its effect on the entire buffer.
> >
> > It seems there is some non-negligible functionality/behavior/feature
> > that has not been documented. Not up to Emacs standards, it appears.
> >
> > It looks like someone perhaps implemented something and just tossed
> > some minimal doc into the manual, in the form of doc-string-like text
> > for a couple functions. Insufficient.
>
> "Compliments" such as these for something that caused me a
> considerable effort to produce where no documentation by the code
> developers existed in the first place is a very efficient method of
> convincing me never to make such efforts again. Not for this
> community, anyway. Thanks a lot!
Please consider it instead as a statement that "the code
developers" for this feature (whatever it might be) should
themselves have documented it. Which is also what I think
you suggest.
My plaint wrt what the user sees now (incomplete doc) is
essentially the same as your plaint that the code developers
did not provide adequate doc. I don't at all complain about
your effort to improve a complete lack by providing something
helpful.
You improved things by adding some explanation. I made a
(minor) effort to improve things after that, by saying that,
IMO, the doc is still not sufficient.
My guess is that those responsible for adding this feature
are the best placed to provide the technical content (if not
necessarily the wording) for telling users what it is.
I don't know what that content is - dunno what the feature is.
As a user learning about this question for the first time, I
searched the manuals for "sub-mode" and similar expressions
to learn more, and came up empty-handed. I reported that.
Perhaps you too have only a partial feel for this feature.
I have no gripe whatsoever with what you've done to help us
understand this, Eli. Quite the contrary.
Had you not documented this at all, I would not have noticed
it and would not have posed questions about it. You need not
be defensive about my saying the doc is incomplete here.
You can be proud that you tried to make it more complete.
Thank you for that. In fact, I thank Emacs everyday for your
unflagging concern about the doc and your efforts to maintain
and improve it.
This concern with doc is an Emacs tradition that dates from
Day One and for which RMS was always a prominent advocate and
participant. Today, you remain the main stalwart in this
endeavor. Thank goodness you are still at it.
next parent reply other threads:[~2016-03-24 14:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20160322022539.16038.77264@vcs.savannah.gnu.org>
[not found] ` <<E1aiC0q-0004DL-40@vcs.savannah.gnu.org>
[not found] ` <<jwvoaa6u36j.fsf-monnier+emacsdiffs@gnu.org>
[not found] ` <<8737riqouj.fsf@gmail.com>
[not found] ` <<221845e0-b194-433e-bfbc-105272ae5752@default>
[not found] ` <<87twjyp21k.fsf@gmail.com>
[not found] ` <<a15ff45f-aef0-4e89-b428-dd1d58a85960@default>
[not found] ` <<56F242E0.7060004@online.de>
[not found] ` <<877fgtpfrw.fsf@gmail.com>
[not found] ` <<56F293E7.2000703@online.de>
[not found] ` <<87a8lpnusg.fsf@gmail.com>
[not found] ` <<83r3f12oo5.fsf@gnu.org>
[not found] ` <<56F2D156.9040401@online.de>
[not found] ` <<83k2kt2i51.fsf@gnu.org>
[not found] ` <<56F2E643.4060903@online.de>
[not found] ` <<592bbafa-76ae-49d9-b5cd-644b3619a0d8@default>
[not found] ` <<838u1835si.fsf@gnu.org>
2016-03-24 14:41 ` Drew Adams [this message]
2016-03-24 16:12 ` [Emacs-diffs] widen-limits c331b66: Implement buffer-widen-limits functionality Eli Zaretskii
[not found] ` <<83zitn26t0.fsf@gnu.org>
2016-03-24 16:24 ` Drew Adams
[not found] <20160322022539.16038.77264@vcs.savannah.gnu.org>
[not found] ` <E1aiC0q-0004DL-40@vcs.savannah.gnu.org>
2016-03-22 12:08 ` Stefan Monnier
2016-03-22 19:44 ` Vitalie Spinu
2016-03-22 19:56 ` Drew Adams
2016-03-22 22:42 ` Vitalie Spinu
2016-03-23 0:44 ` Drew Adams
2016-03-23 7:16 ` Andreas Röhler
2016-03-23 11:58 ` Vitalie Spinu
2016-03-23 13:02 ` Andreas Röhler
2016-03-23 14:17 ` Vitalie Spinu
2016-03-23 15:34 ` Eli Zaretskii
2016-03-23 17:24 ` Andreas Röhler
2016-03-23 17:55 ` Eli Zaretskii
2016-03-23 18:53 ` Andreas Röhler
2016-03-23 21:57 ` Drew Adams
2016-03-23 22:13 ` Vitalie Spinu
2016-03-23 23:03 ` Drew Adams
2016-03-24 3:38 ` Eli Zaretskii
2016-03-24 12:24 ` Dmitry Gutov
2016-03-24 15:56 ` Eli Zaretskii
2016-03-28 1:03 ` Dmitry Gutov
2016-03-24 3:37 ` Eli Zaretskii
2016-03-23 17:14 ` Andreas Röhler
2016-03-24 0:03 ` Vitalie Spinu
2016-03-24 0:37 ` Drew Adams
2016-03-24 2:36 ` Vitalie Spinu
2016-03-24 13:53 ` Drew Adams
2016-03-24 13:57 ` Dmitry Gutov
2016-03-24 14:31 ` Drew Adams
2016-03-24 14:56 ` Stefan Monnier
2016-03-24 15:13 ` Drew Adams
2016-03-24 15:20 ` Stefan Monnier
2016-03-24 7:00 ` Andreas Röhler
2016-03-23 14:29 ` Drew Adams
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=9307373f-0ecd-4825-8b9c-20280b9c92c0@default \
--to=drew.adams@oracle.com \
--cc=andreas.roehler@online.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=spinuvit@gmail.com \
/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).