all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Learning "my emacs" from the start
Date: Sun, 20 Apr 2014 16:12:29 +0200	[thread overview]
Message-ID: <87d2gc5bua.fsf@zigzag.favinet> (raw)
In-Reply-To: <83eh0sfeiy.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Apr 2014 14:04:21 +0300")

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

() Eli Zaretskii <eliz@gnu.org>
() Sun, 20 Apr 2014 14:04:21 +0300

   Really?  I thought they were one and the same, at least in most
   quarters.

For some (maybe most) people, making the effort to understand what makes
a goal impractical in the eyes of the experienced is the most important
practice to undertake.  (Insert destination/journey blurb here.)

If OP can vaunt the small hurdles along the way, who knows, maybe the
big ones we (think we) see will prove easily surmountable after all
(with a SMOP :-D).  This is how the "old" can learn from the "young".

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

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

  reply	other threads:[~2014-04-20 14:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 20:10 Learning "my emacs" from the start (was: Generating a listing of all symbols) Hans BKK
2014-04-19 20:57 ` Emanuel Berg
2014-04-20  8:06 ` Eli Zaretskii
2014-04-20 10:39   ` Learning "my emacs" from the start Thien-Thi Nguyen
2014-04-20 11:04     ` Eli Zaretskii
2014-04-20 14:12       ` Thien-Thi Nguyen [this message]
2014-04-20 14:13         ` Eli Zaretskii
2014-04-22  8:47           ` Nicolas Richard
2014-04-22 16:40             ` Eli Zaretskii
2014-04-20 13:00     ` Florian v. Savigny
2014-04-20 13:29       ` Florian v. Savigny
2014-04-20 14:50       ` Thien-Thi Nguyen
2014-04-21  8:26         ` Florian v. Savigny
     [not found]         ` <mailman.19974.1398068777.10748.help-gnu-emacs@gnu.org>
2014-04-21 13:12           ` Hans BKK
     [not found] ` <mailman.19908.1397981214.10748.help-gnu-emacs@gnu.org>
2014-04-20 13:23   ` Learning "my emacs" from the start (was: Generating a listing of all symbols) Rusi
2014-04-20 17:13     ` Bob Proulx
2014-04-20 18:51       ` Eli Zaretskii
     [not found]       ` <mailman.19947.1398019903.10748.help-gnu-emacs@gnu.org>
2014-04-21 14:37         ` Rusi
2014-04-21 19:01           ` Bob Proulx
2014-04-21 20:16             ` Robert Thorpe
2014-04-21 20:22             ` Robert Thorpe
2014-04-21 21:00             ` Eli Zaretskii
     [not found]           ` <mailman.20014.1398106904.10748.help-gnu-emacs@gnu.org>
2014-04-22  1:37             ` Rusi
2014-04-20 17:12 ` Hans BKK
2014-04-20 20:36   ` Robert Thorpe
2014-04-20 20:41   ` Emanuel Berg

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=87d2gc5bua.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=help-gnu-emacs@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.