emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: [PATCH] Make org-narrow-to-subtree usable out of Org mode [8.2.7b (release_8.2.7b-6-g07d470 @ /home/youngfrog/sourcetrees/org-mode/lisp/)]
Date: Thu, 24 Jul 2014 15:28:52 +0200	[thread overview]
Message-ID: <878uni7unf.fsf@geodiff-mac3.ulb.ac.be> (raw)
In-Reply-To: <87bnsfrycn.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 24 Jul 2014 09:48:40 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> `org-narrow-to-subtree' is an Org function. I don't think it should
> bother about non Org mode buffers.

It's an Org function that grafts itself to narrow-map, which is globally

I think it should try to have at least a sensible error message. The
current "Before first headline" isn't quite clear (my patch doesn't
address this, btw).

>> It looked pretty easy to fix, so here is my suggestion, below. It should
>> be rather harmless since it only affects non-Org buffers (and might have
>> the nice side effect of allowing other commands to run in those buffers
>> -- but I haven't checked.)
> There was a discussion recently about making it easier to use some Org
> features outside of Org.

I guess you're talking about

> IIRC, the conclusion was that should not happen
> at the core level, but as an external layer (e.g., a minor mode).

If core Org functions only care about org-mode buffers, I guess it is
hard to make a minor mode that reuses some of Org to do its job. Unless
that mode is itself in the core of course. e.g. orgstruct-mode does that
and it needs some "core support".

Anyway, my goal isn't to discuss a whole org minor mode.


  reply	other threads:[~2014-07-24 13:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 17:48 Bug: [PATCH] Make org-narrow-to-subtree usable out of Org mode [8.2.7b (release_8.2.7b-6-g07d470 @ /home/youngfrog/sourcetrees/org-mode/lisp/)] Nicolas Richard
2014-07-24  7:48 ` Nicolas Goaziou
2014-07-24 13:28   ` Nicolas Richard [this message]
2014-07-24 14:02     ` Nicolas Goaziou
2014-07-24 14:25       ` Nicolas Richard
2014-07-24 15:00         ` Thorsten Jolitz
2014-07-25  9:13         ` Nicolas Goaziou
2014-07-28 14:18         ` Bastien
2014-07-30 14:51           ` Nicolas Richard
2014-07-30 15:20             ` Thorsten Jolitz
2014-07-30 15:37               ` Nicolas Richard
2014-07-30 16:30                 ` Thorsten Jolitz
2014-07-31  8:00                   ` Nicolas Richard
2014-07-28 14:15 ` Bastien

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:

  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=878uni7unf.fsf@geodiff-mac3.ulb.ac.be \
    --to=theonewiththeevillook@yahoo.fr \
    --cc=emacs-orgmode@gnu.org \


* 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


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