emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Wagner <torsten.wagner@gmail.com>
To: Sanjib Sikder <sanjibju2002@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Structure editing
Date: Fri, 8 Feb 2013 22:18:28 +0100	[thread overview]
Message-ID: <CAPaq-gMuF_5LawZUZBOhYNywt5p6bo1bA7X7KMs74AeD0N-eZQ@mail.gmail.com> (raw)
In-Reply-To: <CAL1SgUoL+sdGZuYLybqzSrU==rspD+Obac9LM=JC27fNNRnGpg@mail.gmail.com>

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

Hi,

this is a easy one ;)

Unfolded state:
===========
* Heading 1
** Heading 1-1
** Heading 1-2
* ---------------------------------
* Heading 2
** Heading 2-1
** Heading 2-2

Folded state
=========
* Heading 1
* ----------------------------------
* Heading 2


Done, problem solved :D

Torsten


On 8 February 2013 10:08, Sanjib Sikder <sanjibju2002@gmail.com> wrote:

> " Is this document aimed for export to a specific backend," - NO
> " or is it just the way you want the org buffer to look?" - YES
>
> The org-mode is a fantastic tool the way it is. I was just enquiring
> whether it is possible or not.
>
> In one of my document I have to write few lines like "The following case
> is applicable only if you want to do this or that." and then a tree
> structure which instructs something.
>
> Orgmode is powerful enough to design the document in a way to meet the
> objective. I will think about that. Thanks to all of you.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1521 bytes --]

  reply	other threads:[~2013-02-08 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 19:57 Structure editing Sanjib Sikder
2013-02-07 20:48 ` Suvayu Ali
2013-02-08  5:36   ` Sanjib Sikder
2013-02-08  8:24     ` Suvayu Ali
2013-02-08  8:51     ` David Rogers
2013-02-08  9:08       ` Sanjib Sikder
2013-02-08 21:18         ` Torsten Wagner [this message]
2013-02-08  9:31     ` A line in between top level headings (was: Structure editing) Karl Voit

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=CAPaq-gMuF_5LawZUZBOhYNywt5p6bo1bA7X7KMs74AeD0N-eZQ@mail.gmail.com \
    --to=torsten.wagner@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sanjibju2002@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).