unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 49330@debbugs.gnu.org
Subject: bug#49330: Customization buffer should also offer printing code snippets
Date: Sat, 03 Jul 2021 09:49:18 +0300	[thread overview]
Message-ID: <83pmvzj3ip.fsf@gnu.org> (raw)
In-Reply-To: <87r1gf6gwe.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Sat, 03 Jul 2021 14:38:41 +0800)

> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: 49330@debbugs.gnu.org
> Date: Sat, 03 Jul 2021 14:38:41 +0800
> 
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> EZ> You mean, what Emacs will write into the init file to save your
> EZ> customizations?
> 
> Yes.
> 
> EZ> Why is that needed?
> 
> So the user can be in full control. RMS knows the feeling.

The user _is_ in control, you are just annoyed by the way this can be
done now.

> The user wants a piece of code that he can stick into his .emacs,
> safe from having to fight with a robot on who can edit a file.
> The user wants to put it into a file that only he is editing.

See the variable custom-file, through which you can control into which
file Emacs will write the customization form when you click Save.

> EZ> If you want to customize your
> EZ> faces in Lisp, the recommended way is to use set-face-attribute
> EZ> instead, not custom-set-faces.
> 
> OK, good. then have the snippet be a set-face-attribute snippet.
> 
> The documentation would be: "Here is a snippet you can paste into your
> .emacs file manually, if you don't feel comfortable allowing the robot
> maintain your customizations."

Sounds like too much effort for very little gain to me.





  reply	other threads:[~2021-07-03  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 14:16 bug#49330: Customization buffer should also offer printing code snippets 積丹尼 Dan Jacobson
2021-07-02 17:24 ` Eli Zaretskii
2021-07-03  6:08   ` 積丹尼 Dan Jacobson
2021-07-03  6:29     ` Eli Zaretskii
2021-07-03  6:38       ` 積丹尼 Dan Jacobson
2021-07-03  6:49         ` Eli Zaretskii [this message]
2021-07-04 14:02           ` Lars Ingebrigtsen
2021-07-08  8:03           ` 積丹尼 Dan Jacobson

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=83pmvzj3ip.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=49330@debbugs.gnu.org \
    --cc=jidanni@jidanni.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).