emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Anders Waldenborg <anders@0x63.nu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Personal wiki
Date: Tue, 26 Jul 2011 02:51:08 +0200	[thread overview]
Message-ID: <87wrf5q2yr.fsf@gnu.org> (raw)
In-Reply-To: <20110724195759.GD5700@0x63.nu> (Anders Waldenborg's message of "Sun, 24 Jul 2011 21:57:59 +0200")

Hi Anders,

Anders Waldenborg <anders@0x63.nu> writes:

> On Sun, Jul 24, 2011 at 09:22:57PM +0200, Bastien wrote:
>> Org has `C-x n s' to narrow to a subtree.
>
> Right. The difference is that aw-org-pw re-narrows when navigating to
> a different section. Maybe that is a feature that would be useful
> directly in org instead. Maybe pre/post-link-follow hooks could do
> that?

Mmhh.. do you really use this often?  I mean: it's quite useful to work
from a wide buffer when navigating -- narrowing is just for quickly
focusing on something.  (But maybe I should rather test your file and
see how useful it can be.)

> Also aw-org-pw autowidens on isearch. (the reason for that is that when
> used as a personal wiki each section should be small, so searching is
> seldom required within a section, and searching the full "wiki" is
> more useful).

Okay - since narrowing in Org is not that frequent and Org files can 
be very large, I guess it's better to *not* auto-widen on isearch.

> But the more I think about it maybe I should just use [[...]] as it
> would greatly simplify the implementation.

:)

> Thanks for your input!

You're welcome,

-- 
 Bastien

  reply	other threads:[~2011-07-26  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 21:25 Personal wiki Anders Waldenborg
2011-07-24 19:22 ` Bastien
2011-07-24 19:57   ` Anders Waldenborg
2011-07-26  0:51     ` Bastien [this message]
2011-07-29 20:58       ` Anders Waldenborg

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=87wrf5q2yr.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=anders@0x63.nu \
    --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).