unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Neil Cerutti <leadvoice@email.com>
Subject: Re: indentation, setting variables, commands, and M-x
Date: 3 Feb 2006 21:05:09 +0100	[thread overview]
Message-ID: <slrndu7dqo.1oc.leadvoice@FIAD06.norwich.edu> (raw)
In-Reply-To: mailman.38.1138993306.2860.help-gnu-emacs@gnu.org

On 2006-02-03, Drew Adams <drew.adams@oracle.com> wrote:
> In this case, you want to search the manual for "indent" or
> "indentation".  Looking through the explanation of Info mode (from
> `C-h m'), you'll see that `i' looks up a topic in the index, and `s'
> searches the manual for a term.  Using either `i indentation' or `s
> indentation' will soon get you to the part of the manual that
> answers most of your questions (`i indentation' will take you there
> directly, because there is an "indentation" index entry).

It's a slight pain when Emacs uses vocabulary that is hard to guess,
e.g., fill for line-wrapping, and font-lock for syntax coloring. In
these situations, s and i aren't much good.

Those issues are slowly sorting themselves out for me, though.

> Emacs is a self-documenting system - perhaps the first such and
> still probably the best. Spend some time learning the help commands
> first (`C-h ?'), then explore the manual a bit. You'll soon be
> hooked.

I'm finally learning emacs because the functional programming world
seems to rely on it for so many of their IDEs. I'm on a strict regimen
of NO VIM until I'm finally confortable with it. Learning vim first
was just a historical accident, after all.

-- 
Neil Cerutti
When you're in the public eye, it's wrong to cheat on someone,
unless you're very careful. If you're normal and no one's going
to know, then do it. --Paris Hilton

  parent reply	other threads:[~2006-02-03 20:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  5:18 indentation, setting variables, commands, and M-x John M. Gabriele
2006-02-03  7:48 ` Eli Zaretskii
2006-02-03  8:54 ` Alan Mackenzie
2006-02-03 16:49   ` Cameron Desautels
2006-02-03  9:53 ` Peter Dyballa
2006-02-03 15:52 ` Drew Adams
2006-02-03 19:21 ` john_sips_tea
2006-02-03 19:27   ` john_sips_tea
2006-02-03 23:12   ` Peter Dyballa
2006-02-06 18:36     ` Kevin Rodgers
2006-02-06 21:11       ` Peter Dyballa
     [not found] ` <mailman.38.1138993306.2860.help-gnu-emacs@gnu.org>
2006-02-03 20:05   ` Neil Cerutti [this message]
2006-02-04 11:13     ` Eli Zaretskii
2006-02-03 20:55   ` john_sips_tea
2006-02-04 17:27     ` Drew Adams
     [not found] <mailman.31.1139095080.2870.help-gnu-emacs@gnu.org>
2006-02-05  3:46 ` John M. Gabriele
2006-02-05 19:52   ` Eli Zaretskii

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=slrndu7dqo.1oc.leadvoice@FIAD06.norwich.edu \
    --to=leadvoice@email.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).