emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Cian OConnor <cian.oconnor@gmail.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Narrow tSparse Trees layout
Date: Tue, 04 Aug 2009 14:51:57 +0100	[thread overview]
Message-ID: <827hxjr8jm.fsf@gmail.com> (raw)
In-Reply-To: <87hbwqhutk.fsf@bzg.ath.cx> (Bastien's message of "Mon, 03 Aug 2009 03:17:10 +0800")

Bastien <bastienguerry@googlemail.com> writes:

> Hi Cian,
>> Its just that when drafting papers I tend to have lots and lots of
>> indentation in early drafts, and while narrowing trees is a godsend, the
>> unnecessary (for my purposes) indentation is slightly annoying.
>
> If the purpose of such a temporary display is to make the export render
> the structure of the narrowed buffer as if it was a top-level subtree,
> then I agree this is useful.  You can already achieve this by selecting
> the whole narrowed subtree (with transient-mark-mode on) and exporting
> the region.

Not really. Its simply a convenience method that I can probably hack for 
myself, but didn't want to if it already existed. Its simply when I'm 
drafting I tend to work in subtrees, and it becomes (for my purposes)
quite unwieldy when working with large trees (as I tend to). The indent
when I'm working with the narrowed buffer is a waste of space, and it
also makes it difficult for me to work out what level I'm working at
with a simple eyeball at the structure.

However I can quite cheerfully see that this is not something most
people would want/need.

> But maybe a narrowed tree should be considered as a selected region by
> default...  

Yes it probably should.

  reply	other threads:[~2009-08-04 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 21:13 Sparse Trees layout Cian OConnor
2009-07-31  0:10 ` Bastien
2009-07-31 14:22   ` Narrow tSparse " Cian OConnor
2009-07-31 14:46     ` Nick Dokos
2009-08-02 19:17     ` Bastien
2009-08-04 13:51       ` Cian OConnor [this message]
2009-08-04 17:20         ` Samuel Wales

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=827hxjr8jm.fsf@gmail.com \
    --to=cian.oconnor@gmail.com \
    --cc=bastienguerry@googlemail.com \
    --cc=emacs-orgmode@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.
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).