emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: structure editing in brainstorming mode
Date: Mon, 29 Dec 2008 11:36:26 -0500	[thread overview]
Message-ID: <871vvrym45.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <f46c52560812282158k1a98264bqf62e34c2d2f9b023@mail.gmail.com> (Rustom Mody's message of "Mon\, 29 Dec 2008 11\:28\:42 +0530")

"Rustom Mody" <rustompmody@gmail.com> writes:

> 1. Multiple heading demotion
>
> Lets say I start writing down some points maybe with/without some
> additional text
> * Cat
> * Dog
>
> And now I decide to put all these into a superheading 'My Pets'
> The only way I know is to enter
> * My Pets
> before Cat and then demote each subtree -- if there were not two but
> ten I'd have to do that 10 times

This sounds like a great use for a keyboard macro

Hit S-Tab until you get Contents view which shows headlines only (the
rest of the content is folded) and position the cursor on the first
headline to be demoted

C-x (
M-S-right
M-x org-forward-same-level
C-x )

Then just C-x e to repeat the macro and demote the current headline and
move forward to the next one.  If you're demoting consecutive entries
then you can do C-x e for the first and just 'e' for each successive one
to repeat the macro. (eg. C-x e e e e demotes this headline and the 3
following it)

>
> 2. Converting heading type
>
> Sometimes one assumes that the points are 'small' and so are entered
> as + points. Thus
> * Pets
>   + Cat
>   + Dog
> and then at some point it emerges that the +es had better be changed
> to headings that is (the requisite number of) *s.  Any easy way of
> doing that?

You can just use query replace for this

Highlight the entries to convert and then

C-M-%

and change 
'^  \+'
to
'**'  (or '***' if you are using odd levels only)

HTH,
-Bernt

  parent reply	other threads:[~2008-12-29 16:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  5:58 structure editing in brainstorming mode Rustom Mody
2008-12-29 12:51 ` Matthew Lundin
2008-12-30 23:55   ` Carsten Dominik
2008-12-31  6:04     ` Rustom Mody
2008-12-31  8:07       ` Carsten Dominik
2008-12-31 11:36         ` Daniel Clemente
2008-12-31 13:28           ` Carsten Dominik
2008-12-31 13:33             ` Daniel Martins
2009-01-01  6:42             ` Rustom Mody
2009-01-01  8:58               ` Carsten Dominik
2009-01-01 22:53         ` Matthew Lundin
2008-12-29 16:36 ` Bernt Hansen [this message]
2008-12-29 17:15   ` Nick Dokos
2008-12-30  0:50 ` Olaf Dietsche
2008-12-30 14:11   ` Rustom Mody
2008-12-31  0:23     ` Carsten Dominik
     [not found] <200812291702.mBTH2sVD004384@bp34.u.washington.edu>
2008-12-29 19:44 ` Scott Otterson
2008-12-29 20:10   ` Matthew Lundin

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vvrym45.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=rustompmody@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).