emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Omar Antolín Camarena" <omar@matem.unam.mx>
To: "Omar Antolín Camarena" <omar@matem.unam.mx>, emacs-orgmode@gnu.org
Subject: Re: Org mode pollutes the narrow-map
Date: Fri, 23 Aug 2019 05:10:30 -0500	[thread overview]
Message-ID: <CAL03oyL1bt7mJ_geMSUmYEPuze-NYxyYgcSiTagCT5hg=AnH6w@mail.gmail.com> (raw)
In-Reply-To: <87mug0z34a.fsf@nicolasgoaziou.fr>

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

Great, thanks!

On Fri, Aug 23, 2019, 3:40 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Omar Antolín Camarena <omar@matem.unam.mx> writes:
>
> > Hello everyone,
> >
> > Does it seems a little rude that Org mode binds its own narrowing
> commands in the global narrow-map?
> >
> > You can find this in org.el starting at line 19018:
> >
> > #+begin_src emacs-lisp
> >   ;;;; Narrow map
> >   (org-defkey narrow-map "s" #'org-narrow-to-subtree)
> >   (org-defkey narrow-map "b" #'org-narrow-to-block)
> >   (org-defkey narrow-map "e" #'org-narrow-to-element)
> > #+end_src
> >
> > I don't need or really want those commands bound in non-org buffers.
> > I think it would be better to bind them (to C-x n s, C-x n b and C-x
> > n e) in org-mode-map. This is the approach taken by AUCTeX, for
> > example. (To be clear, I mean AUCTeX has some narrowing commands and
> > it binds them to C-x n e and C-x n g in its own keymaps.)
>
> It sounds reasonable. I changed the bindings in master. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>

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

      reply	other threads:[~2019-08-23 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23  0:47 Org mode pollutes the narrow-map Omar Antolín Camarena
2019-08-23  8:40 ` Nicolas Goaziou
2019-08-23 10:10   ` Omar Antolín Camarena [this message]

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='CAL03oyL1bt7mJ_geMSUmYEPuze-NYxyYgcSiTagCT5hg=AnH6w@mail.gmail.com' \
    --to=omar@matem.unam.mx \
    --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).