From: Jude DaShiell <jdashiel@shellworld.net>
To: Steven Degutis <sbdegutis@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: org-mode tutorial?
Date: Sun, 28 Apr 2013 03:21:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.01.1304280319350.30100@freire1.furyyjbeyq.arg> (raw)
In-Reply-To: <CACeWA3gFqmWHv330xk==XYZ5w5UGMTQEAnx3B7-ePv0SD9f9OQ@mail.gmail.com>
My guess is hierarchical lists are made hierarchical by means of different
indentation levels. You start out with top hierarchy level and a first
plain list. Then move one level down hierarchy by using one indent level.
On Sat, 27 Apr 2013, Steven Degutis wrote:
> I've tried a few times to get started using org-mode for hierarchical
> lists. But every single time I try to look for some tutorials or intro
> pages, I get an overwhelming list, and the vast majority of them don't
> even seem to talk about working with hierarchical lists, but rather
> all the *other* things you can do in org-mode.
>
> Can someone please point me to a really basic tutorial or explanation
> on how to use org-mode to create hierarchical lists? I basically mean
> something like html's [ul] and [li] elements, nested.
>
> -Steven
>
>
---------------------------------------------------------------------------
jude <jdashiel@shellworld.net>
Microsoft, windows is accessible. why do blind people need screen readers?
next prev parent reply other threads:[~2013-04-28 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 19:21 org-mode tutorial? Steven Degutis
2013-04-27 19:25 ` Teemu Likonen
2013-04-28 6:50 ` Bastien
2013-04-28 7:18 ` Jude DaShiell
2013-04-28 9:07 ` Tamas K Papp
2013-04-28 7:21 ` Jude DaShiell [this message]
2013-04-28 7:58 ` Bastien
2013-04-28 11:31 ` actual html or something else? [was: Re: org-mode tutorial?] ken
2013-04-29 14:57 ` Bastien
2013-04-29 15:32 ` Bastien
2013-04-29 18:28 ` ken
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=alpine.BSF.2.01.1304280319350.30100@freire1.furyyjbeyq.arg \
--to=jdashiel@shellworld.net \
--cc=help-gnu-emacs@gnu.org \
--cc=sbdegutis@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).