unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: About `name' in loadup.el
Date: Wed, 13 Mar 2013 11:35:31 +0100	[thread overview]
Message-ID: <87620vlh8s.fsf@zigzag.favinet> (raw)
In-Reply-To: 20130310210249.11a8a74c64af0c126605df8f@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

() Xue Fuqiao <xfq.free@gmail.com>
() Sun, 10 Mar 2013 21:02:49 +0800

   As I said in this thread, I usually do many things before asking a
   questions:
   http://lists.gnu.org/archive/html/help-gnu-emacs/2013-01/msg00076.html

One thing that you can add to that list is to try executing code (that
you feel is safe), to see how it behaves in reality.  If the snippet is
small and relatively self-contained (as in this particular case), it can
be fun to wrap it in a command and edebug it.  For example, in *scratch*:

 (defun ttn-try ()
   (interactive)
   (... some code ...))
 
 (global-set-key [(meta f1)] 'ttn-try)

Then:
- Place point on the ‘defun’ and do ‘M-x edebug-defun RET’.
- Invoke (via ‘M-f1’), step through (via ‘SPC’), eval (via ‘e’), etc.

There is also ‘edebug-eval-top-level-form’, which is easier to work with
(less preparation required).  I use ‘edebug-defun’ out of habit, mostly.

   > Adopting this approach is beneficial in another way: You will no
   > longer need to ask the somewhat pointless question "Can anybody
   > help?".  The answer to that question is always "yes".  (Likewise,
   > the answer to "Who can help?" must necessarily include "Xue
   > Fuqiao". :-D)

   I won't close my request for help with semantically-null questions
   like “Can anyone help?” any more, because they are superfluous and
   annoying — like what you said.

Well, the truth is i have a lot of practice being superfluous and
annoying.  You could say i'm an expert on this subject!  :-D

Anyway, Emacs is cool because you can study it also "from the inside".

-- 
Thien-Thi Nguyen
GPG key: 4C807502

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2013-03-13 10:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10  0:11 About `name' in loadup.el Xue Fuqiao
2013-03-10  0:44 ` Pascal J. Bourguignon
2013-03-10  3:51 ` Eli Zaretskii
2013-03-10 11:27 ` Thien-Thi Nguyen
2013-03-10 13:02   ` Xue Fuqiao
2013-03-13 10:35     ` Thien-Thi Nguyen [this message]
2013-03-13 11:10       ` Xue Fuqiao
  -- strict thread matches above, loose matches on Subject: below --
2013-03-10  6:38 Xue Fuqiao
2013-03-10  6:49 ` Jambunathan K
2013-03-10  7:07   ` Xue Fuqiao
2013-03-10 20:00     ` Andy Moreton
2013-03-10 22:37       ` Xue Fuqiao

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=87620vlh8s.fsf@zigzag.favinet \
    --to=ttn@gnuvola.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=xfq.free@gmail.com \
    /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.
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).