From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: monnier@iro.umontreal.ca, bruce.connor.am@gmail.com, emacs-devel@gnu.org
Subject: Re: [elpa] master 9173a44 1/2: [Fix #12] Don't autodisable beacon on hl-line-mode
Date: Mon, 19 Oct 2015 19:19:57 +0300 [thread overview]
Message-ID: <83vba2g79u.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2cBrikaUo69434=4ySrQn7Leyvcf=TP=Eiahi-0FWrtg@mail.gmail.com>
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Mon, 19 Oct 2015 11:28:46 -0400
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Artur Malabarba <bruce.connor.am@gmail.com>,
> Emacs developers <emacs-devel@gnu.org>
>
> Nothing is wrong with the style. I was mainly pointing out that the
> self-opinion style of text contradicted with what is recommended.
Sorry, my misunderstanding.
> - It is recommended that the user does not manually edit the Customize
> generated code blocks but a text I quoted says that the author did
> that it was fine.
> - Also the author does not use Customize most of the times whereas for
> a new user it is recommended to do so.
Indeed, that manual is in dire need of updates. Feel free to bring it
up to speed with the current development and latest use
recommendations.
Thanks in advance.
prev parent reply other threads:[~2015-10-19 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151017213254.5317.59042@vcs.savannah.gnu.org>
[not found] ` <E1ZnZ5y-0001ON-4Z@vcs.savannah.gnu.org>
2015-10-18 3:20 ` [elpa] master 9173a44 1/2: [Fix #12] Don't autodisable beacon on hl-line-mode Stefan Monnier
2015-10-18 18:48 ` Artur Malabarba
2015-10-19 0:56 ` Stefan Monnier
2015-10-19 5:56 ` Marcin Borkowski
2015-10-19 13:31 ` Stefan Monnier
2015-10-19 14:00 ` Kaushal Modi
2015-10-19 14:20 ` Drew Adams
2015-10-19 14:40 ` Eli Zaretskii
2015-10-19 15:28 ` Kaushal Modi
2015-10-19 16:19 ` Eli Zaretskii [this message]
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=83vba2g79u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.