unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hans BKK <hansbkk@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Generating a listing of all symbols (16K+) and labeling subsets
Date: Sat, 19 Apr 2014 13:15:21 -0700 (PDT)	[thread overview]
Message-ID: <613d311e-c223-407a-b741-5f188bd6d0d3@googlegroups.com> (raw)
In-Reply-To: <38d1beb3-fffd-4718-ae10-be9646ac4a63@googlegroups.com>


On Saturday, April 19, 2014 12:34:31 PM UTC-4, Robert Thorpe wrote:
> Total noob here - and non-programmer to boot, as will become 
> immediately apparent from the code below - so please be gentle. 
> 
> Before I start getting to know emacs as an end-users - which I'm 
> highly motivated to do, despite the amazingly steep learning curve to 
> do the most basic things - I plan to of course highly customize my 
> emacs environment to suit my needs, before starting the muscle-memory 
> training required to become efficient. 

There's no one right way to learn Emacs.  But, I think the way you're 
choosing is a lot of work. 

You can start off using it for everyday editing, that's what I did and 
what lots of people do.  I expect you've done the tutorial and learned 
the keybindings, that's very useful.  Then read a bit of the manual 
and the internet resources occasionally and learn more. 

You only really need to looks for customizations, enable non-default 
packages, etc. when you run into a problem or you feel something is 
inefficient.  Why change the standard behaviour if it's not a problem? 

<snip>

In the interest of keeping this thread focused on the implementation-specific issues rather than the diversions likely from my answer, I've started a new thread for the "pig picture" issues here:

http://groups.google.com/forum/#!topic/gnu.emacs.help/GLhpDW6Ksa8


  parent reply	other threads:[~2014-04-19 20:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18  5:15 Generating a listing of all symbols (16K+) and labeling subsets Hans BKK
2014-04-18 19:01 ` Hans BKK
2014-04-18 20:47   ` Nicolas Richard
2014-04-19  1:23 ` Hans BKK
2014-04-19  2:16   ` John Mastro
2014-04-19  2:25 ` Hans BKK
2014-04-19  2:50   ` Hans BKK
2014-04-19  4:24   ` Drew Adams
2014-04-19 20:15 ` Hans BKK [this message]
2014-04-23  4:11 ` Hans BKK
2014-04-23  7:40   ` Florian v. Savigny
     [not found]   ` <<874n1klchv.fsf@bertrandrussell.Speedport_W_723V_1_32_000>
2014-04-23 15:07     ` Drew Adams
2014-04-23 13:22 ` Hans BKK
2014-04-24  2:30 ` Hans BKK
  -- strict thread matches above, loose matches on Subject: below --
2014-04-18  2:34 hansbkk
2014-04-18  2:09 hansbkk
2014-04-18  7:19 ` Thien-Thi Nguyen
2014-04-18 10:09   ` Thorsten Jolitz
     [not found]   ` <mailman.19825.1397815734.10748.help-gnu-emacs@gnu.org>
2014-04-18 15:00     ` Hans BKK
     [not found] ` <mailman.19813.1397805348.10748.help-gnu-emacs@gnu.org>
2014-04-18 14:55   ` Hans BKK
2014-04-18 15:27     ` Nicolas Richard
2014-04-19 16:34 ` Robert Thorpe

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=613d311e-c223-407a-b741-5f188bd6d0d3@googlegroups.com \
    --to=hansbkk@gmail.com \
    --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.
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).