From: Matt Price <moptop99@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-writers-room sort of works! just in time for NaNoWriMo
Date: Tue, 5 Nov 2013 04:54:42 -0500 [thread overview]
Message-ID: <CAN_Dec9eU4pJUZck6kU4LqjcA+DAeqKid0CPPvLh7DAb4w=QsA@mail.gmail.com> (raw)
In-Reply-To: <87a9hkjcli.fsf@gmail.com>
On Mon, Nov 4, 2013 at 12:33 PM, Thorsten Jolitz <tjolitz@gmail.com> wrote:
> Matt Price <moptop99@gmail.com> writes:
>
> Hi Matt,
>
>> Hi Thorsten,
>>
>> Wow, navi-mode really is incredibly cool.
>
> thanks. why not write this on the mailing list - a bit of publicity
> can't hurt ;)
>
oh shoot, sorry! my mistake!
>> I had not tried it before because it failed to load properly on al of
>> hte org files I tested it with. I suspected that I was not following
>> some important convention in the way I structure those files, but now
>> that doesn't seem to be the case. On further investigation, something
>> very strange is going on; the buffers work fine when I close and then
>> reopen them, but anything that has been open for a long time seems to
>> fail to load navi-mode. Have you seen anything like this before?
>
> not really, but I have a very useful command
>
> ,----------------------------------------------------------------
> | nuke-and-eval is an interactive Lisp function in `nukneval.el'.
> |
> | (nuke-and-eval)
> |
> | Attempt to cleanly reevaluate a buffer of elisp code.
> `----------------------------------------------------------------
>
> and when I do this in an outshine buffer, things get messed up sometimes
> ...
>
>> When I run (navi-search-and-switch) in ny test files, I get en error.
>> The issue seems to be (I think!) on line 1247 of navi.el, where
>> "split-string" is passed "headline-string"; but for some reason
>> headline-string is nil. Reading the code, I do not see immediately
>> what the problem could be, but I suspect that some variable has been
>> set by *something* I do in the course of my daily work, and doesn't
>> get reset properly. If you have an idea I'd really appreciate it!
>
> I bet C-h v outline-promotion-headings is nil when you do it in your
> org-mode test file, it should be:
>
> ,------------------------------------------------------------------------
> | outline-promotion-headings is a variable defined in `outshine.el'.
> | Its value is shown below.
> |
> | Automatically becomes buffer-local when set.
> |
> | Documentation:
> | A sorted list of headings used for promotion/demotion commands.
> | Set this to a list of headings as they are matched by `outline-regexp',
> | top-level heading first. If a mode or document needs several sets of
> | outline headings (for example numbered and unnumbered sections), list
> | them set by set, separated by a nil element. See the example for
> | `texinfo-mode' in the file commentary.
> |
> | For more information check the manuals.
> |
> |
> |
> | Value:
> | (("* " . 1)
> | ("** " . 2)
> | ("*** " . 3)
> | ("**** " . 4)
> | ("***** " . 5)
> | ("****** " . 6)
> | ("******* " . 7)
> | ("******** " . 8))
> |
> | Local in buffer `tmp5.org'; global value is nil
> `------------------------------------------------------------------------
>
> I think this is all related to Emacs internals and loading, if you make
> sure outshine-mode is installed properly, especially with this line:
>
> ,------------------------------------------------------------
> | (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
> `------------------------------------------------------------
>
> thinks should work. Maybe you should just restart your Emacs with the
> lines for installing outshine/outorg/navi in you init file and see if
> it works then? Otherwise reverting a buffer (M-x revert-buffer) might
> help in special cases ...
Yes, this is the problem of course. I just copy-pasted the setup code
into my .emacs without looking at it Foolish!
Busy today and likely tomorrow but I'm going to try to rewrite
writers-room as an extension of navi-mode. The navi-mode buffer is so
much superior to my navigation guide, I don't see how I can use mine
anymore...
Thanks!
mtt
>
> Thanks for your report, let me know if it works. I use navi all the time
> with emacs-lisp-mode, picolisp-mode, org-mode and R-mode and did not
> have any problems for a long time now...
>
> --
> cheers,
> Thorsten
prev parent reply other threads:[~2013-11-05 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 4:00 org-writers-room sort of works! just in time for NaNoWriMo Matt Price
2013-11-01 6:07 ` Ivan Andrus
2013-11-01 6:08 ` Alan L Tyree
2013-11-01 9:07 ` Ian Barton
2013-11-01 14:13 ` Matt Price
2013-11-01 14:12 ` Matt Price
2013-11-01 14:45 ` Thorsten Jolitz
2013-11-01 18:28 ` Alan L Tyree
2013-11-03 3:38 ` Matt Price
2013-11-04 1:10 ` Thorsten Jolitz
[not found] ` <CAN_Dec-+rQSqcDcjpFo9MsfuvK3Fc0bRDrMe_NR232XtcguUXg@mail.gmail.com>
[not found] ` <87a9hkjcli.fsf@gmail.com>
2013-11-05 9:54 ` Matt Price [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='CAN_Dec9eU4pJUZck6kU4LqjcA+DAeqKid0CPPvLh7DAb4w=QsA@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.com \
/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).