all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "arthur miller" <arthur.miller@live.com>,
	"積丹尼 Dan Jacobson" <jidanni@jidanni.org>,
	"Richard Stallman" <rms@gnu.org>
Cc: 38696@debbugs.gnu.org
Subject: bug#38696: "If you edit it by hand, you could mess it up"
Date: Sun, 22 Dec 2019 09:49:51 -0800 (PST)	[thread overview]
Message-ID: <c3147aa0-decb-403a-9c3e-d223e9455223@default> (raw)
In-Reply-To: <VI1P194MB0429F139BA64450B16B6CC34962F0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM>

>> The user is no longer in full control, but must
>> maintain it via an interface (the menus.)
>
> Actually it says "you should be careful". It does
> not says you should never edit it. I don't think
> you have reason to edit it by hand, especially if
> you redirect customize saves to different file
> then your init, but you certainly can if you wish
> (and know what you are doing).

The most important message about this, for users,
is to let them know that this code is inserted
and _updated (overwritten) automatically_.

That's the _reason_ we warn users not to edit it.

It's not so much because their edits might mess
something up.  It's that they need to be aware
that editing it competes with automatic updating.
If you edit it then you are fighting against
Customize.

If you edit it, and if you never use Customize
(and no code you use ever uses Customize code),
then, yes, the only potential problem is that you
can mess things up for your future Emacs sessions.

But that's not the likeliest scenario.  The real,
more likely problem is that you make a change to
this code and later Customize overwrites your
change - and you might not be aware of that.

IMO, that's what this inserted comment is really
about: letting you know that the code is updated
automatically, and manual and automatic updating
don't mix well - each can overwrite the other.

 


-------- Originalmeddelande --------
Från: 積丹尼 Dan Jacobson <jidanni@jidanni.org> 
Datum: 2019-12-22 01:37 (GMT+01:00) 
Till: Richard Stallman <rms@gnu.org> 
Kopia: 38696@debbugs.gnu.org 
Ämne: bug#38696: "If you edit it by hand, you could mess it up" 

>>>>> "RMS" == Richard Stallman <rms@gnu.org> writes:

RMS> Would you please show us what this looks like?

$ cat .emacs
(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(default ((t (:family "DejaVu Sans Mono" :foundry "PfEd" :slant normal :weight normal :height 218 :width normal)))))

There is no way offered to "decompile" this into something that all
those Emacs manuals talk about when introducing how to edit your .emacs
file.

The user is no longer in full control, but must maintain it via an
interface (the menus.)






  reply	other threads:[~2019-12-22 17:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21  0:02 bug#38696: "If you edit it by hand, you could mess it up" 積丹尼 Dan Jacobson
2019-12-21  6:34 ` Phil Sainty
2019-12-21  8:12   ` 積丹尼 Dan Jacobson
2019-12-21 19:08 ` Richard Stallman
2019-12-22  0:35   ` 積丹尼 Dan Jacobson
2019-12-22 17:04     ` Eli Zaretskii
2019-12-23  2:58     ` Richard Stallman
2019-12-23  3:29       ` 積丹尼 Dan Jacobson
2019-12-22  3:35 ` arthur miller
2019-12-22 17:49   ` Drew Adams [this message]
2019-12-23  0:36     ` 積丹尼 Dan Jacobson
2019-12-24  4:13     ` Richard Stallman
2019-12-24 16:08       ` Drew Adams
2019-12-25  2:37         ` Richard Stallman
2019-12-26  1:03           ` 積丹尼 Dan Jacobson
2020-08-06 10:16 ` Lars Ingebrigtsen

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=c3147aa0-decb-403a-9c3e-d223e9455223@default \
    --to=drew.adams@oracle.com \
    --cc=38696@debbugs.gnu.org \
    --cc=arthur.miller@live.com \
    --cc=jidanni@jidanni.org \
    --cc=rms@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 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.