unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt Armstrong <matt@rfc20.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: 56870@debbugs.gnu.org
Subject: bug#56870: company-dabbrev variable documentation
Date: Mon, 01 Aug 2022 14:49:15 -0700	[thread overview]
Message-ID: <87y1w73a90.fsf@rfc20.org> (raw)
In-Reply-To: <xMpOcpx26Ip-bOPKzWV0lgXI_XK10hijRgDtI6QNT_ECNLjQI_u7gs_KcIlLtC67Aa3M7KDNd940F_A19VgRV54BZgL8u09V2YbzskHPxnw=@proton.me>

uzibalqa <uzibalqa@proton.me> writes:

> On Monday, August 1st, 2022 at 9:24 PM, Matt Armstrong <matt@rfc20.org> wrote:
>> Hope that helps!
>
> It is a shame that documentation does not come with example.  It is
> what is much lacking.

I think the "friendly" way to customize Emacs is intended to be the
customization system:
https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html
In most cases, the customize interface hides lisp level details from the
user.

There is project level goal that most of the useful customizations a
user can do in Emacs should be possible in the customize system, without
using lisp.  This is one reason the help text does not often describe
things with Lisp examples.  They would be of no use to the people using
the Customize interface, and possibly even confusing.

I still think your original point is a good one. I found the one piece
of documentation explaining how to write quoted things in Emacs
documentation, but I could not find a place explaining the conventions
for quoted things mean in Emacs help.  Perhaps another person can find
that, or suggest a way to explain it to new users.





  reply	other threads:[~2022-08-01 21:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  3:54 bug#56870: company-dabbrev variable documentation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:24 ` Matt Armstrong
2022-08-01 21:32   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49     ` Matt Armstrong [this message]
2022-08-01 21:55       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 10:20   ` Lars Ingebrigtsen
2022-08-02 10:34     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 10:07     ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 18:41       ` Matt Armstrong
2022-08-03 18:50         ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 17:09           ` Matt Armstrong
     [not found]           ` <878ro4rl4l.fsf@rfc20.org-N8dpYwc----2>
2022-08-04 21:59             ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:06         ` bug#56870: [PATCH] " YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:41           ` Eli Zaretskii
2022-08-04 17:48             ` Matt Armstrong
2022-08-04 18:25               ` Eli Zaretskii
2022-08-05  9:10             ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:09               ` Eli Zaretskii
2022-08-05 11:36                 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 12:42                 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 13:19                   ` 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=87y1w73a90.fsf@rfc20.org \
    --to=matt@rfc20.org \
    --cc=56870@debbugs.gnu.org \
    --cc=uzibalqa@proton.me \
    /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).