From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: [NEW] navi-mode for org files
Date: Mon, 8 Apr 2013 02:12:41 +0000 (UTC) [thread overview]
Message-ID: <loom.20130408T034830-346@post.gmane.org> (raw)
In-Reply-To: 878v4y9ziu.fsf@gmail.com
Thorsten Jolitz <tjolitz <at> gmail.com> writes:
>
>
> Hi List,
>
> I made navi-mode (=> super-fast buffer navigation, visibility-cycling,
> structure-editing, and much more, with one-key commands in an associated
> read-only *Navi* buffer) work with Org-mode buffers too.
>
> The basic things work, but there are still keyword-searches and
> keybindings to define.
>
Thorsten,
Thanks. This is really helpful.
Some comments:
Maybe you have this on your TODO list, but some things do not work as
I would expect.
In the *Navi:myfile.org* buffer, 1,2,3, Z, N, W are all good.
C-1 N also good.
But C-1 Z, C-2 W don't quite work.
I think the part of the regexp that represents the 'Z' or 'W' search needs
to be wrapped in \( ... \) as the parts beyond
\(^\* \|^[ ^I]*#\+name:[ ^I]*
do not match.
===
I find myself doing "1 n n r 2 r Z w 2 n r Z" to look at successive pieces
of a buffer.
Is there a slicker way to do stuff like this?
===
[snip]
,------------------------------------------------------------------------
> | PS
> |
> | Please note that all this is available for your source code buffers
> | too (e.g. in Emacs Lisp) when you structure them the 'outshine' way.
> |
> | Use outorg.el, outshine.el or navi-mode.el as example files to see what
> | I mean (read comment-section of outshine.el for installation tips).
> |
> | Do 'M-s n' on one of them to open a *Navi* buffer. Try the the
> | commands from list item (5) above and don't forget to checkout command
> | 'e' - it is extremely useful since it opens the subtree at point (or,
> | with prefix, the whole Emacs Lisp buffer) in a temporary Org-mode edit
> | buffer.
> `------------------------------------------------------------------------
>
I cannot seem to get this to work. If I try to execute
;; # #+begin_src emacs-lisp
;; # (require 'outshine)
;; # (add-hook ‘outline-minor-mode-hook ‘outshine-hook-function)
;; # #+end_src
the add-hook returns
Debugger entered--Lisp error: (void-variable ‘outline-minor-mode-hook)
I am running
Org-mode version 8.0-pre (release_8.0-pre-276-g3d3465 @ ...
GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of
2013-03-12 on bob.porkrind.org
Best,
next prev parent reply other threads:[~2013-04-08 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 13:49 [NEW] navi-mode for org files Thorsten Jolitz
2013-04-08 2:12 ` Charles Berry [this message]
2013-04-08 19:27 ` Thorsten Jolitz
2013-04-08 21:41 ` Charles Berry
2013-04-08 22:19 ` Thorsten Jolitz
2013-04-09 1:47 ` Charles Berry
2013-04-09 7:58 ` Thorsten Jolitz
2013-04-08 19:31 ` Thorsten Jolitz
2013-04-09 2:16 ` Charles Berry
2013-04-09 7:52 ` Thorsten Jolitz
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=loom.20130408T034830-346@post.gmane.org \
--to=ccberry@ucsd.edu \
--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).