all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>, 38696@debbugs.gnu.org
Cc: rms@gnu.org
Subject: bug#38696: "If you edit it by hand, you could mess it up"
Date: Sat, 21 Dec 2019 19:34:43 +1300	[thread overview]
Message-ID: <6416dc64-18a6-8c2f-f147-18ba19ad5b7e@orcon.net.nz> (raw)
In-Reply-To: <87eewyr1f4.8.fsf@jidanni.org>

On 21/12/19 1:02 PM, 積丹尼 Dan Jacobson wrote:
> that even contains a warning "If you edit it by hand, you could mess
> it up", meaning for the rest of his life he should just play it safe
> and stick with the menus.

It neither says (nor even hints) that this will be the case "for the
rest of [your] life".  I think it implies that it's possible to avoid
messing it up, provided that you know what you're doing; which in turn
suggests that you might learn how to do that.

Like everything else in Emacs, you can use the documentation and code
in order to gain that understanding, if you choose to.  For those who
choose not to, the warning serves a valuable purpose.


-Phil






  reply	other threads:[~2019-12-21  6:34 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 [this message]
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
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=6416dc64-18a6-8c2f-f147-18ba19ad5b7e@orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=38696@debbugs.gnu.org \
    --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.