unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49330@debbugs.gnu.org
Subject: bug#49330: Customization buffer should also offer printing code snippets
Date: Thu, 08 Jul 2021 16:03:51 +0800	[thread overview]
Message-ID: <87h7h56xlk.5.fsf@jidanni.org> (raw)
In-Reply-To: <87y2aool7h.5.fsf@jidanni.org>

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> See the variable custom-file, through which you can control into which
EZ> file Emacs will write the customization form when you click Save.

Yes, and I then cut code out of .emacs-custom.el and paste it into
.emacs, which I then can share with my several machines, safe from being
overwritten by the robot.

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.

I will never know that, as all I do is make a customization, and then
take what got written, and paste it into my .emacs file.

The entire idea is:
1. A file that nobody writes to except me.
2. Lines of code that, although I don't know how to write, at least I
can paste them into a file fully controlled by me, and then share it to
my several machines.

Anyway, fine, emacs' model is everybody owns only one computer or
several computers and is happy with customizations on computer A being
different that those on computer B, because he never wishes to sync his
.emacs etc.

For me, I want to maintain one .emacs file, *by hand*, and any
differences (root vs. regular user, machine name, window system, I can
simply use lisp "(if ...)" to branch with.

Just like web sites' share buttons offer "embed code you can paste on a
web page", emacs' customization page should also offer printing code snippets.





      parent reply	other threads:[~2021-07-08  8:03 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
2021-07-04 14:02           ` Lars Ingebrigtsen
2021-07-08  8:03           ` 積丹尼 Dan Jacobson [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

  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=87h7h56xlk.5.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=49330@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).