From: Leo Ufimtsev <lufimtse@redhat.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: How to deal with conflicting org-toc?
Date: Fri, 17 Apr 2015 11:45:45 -0400 (EDT) [thread overview]
Message-ID: <1565013277.1255423.1429285545379.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1396287533.1254946.1429285486160.JavaMail.zimbra@redhat.com>
Hello,
There is a build-in org-toc in contrib, that shows a dynamic toc on right side.
And there is org-toc that generates a toc from an org file: https://github.com/snosov1/org-toc
They have a name conflict.
Is three any way to resolve this without forking and renaming the variables?
Thank you
Leo Ufimtsev | Intern Software Engineer @ Eclipse Team
next parent reply other threads:[~2015-04-17 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1396287533.1254946.1429285486160.JavaMail.zimbra@redhat.com>
2015-04-17 15:45 ` Leo Ufimtsev [this message]
2015-04-17 15:52 ` How to deal with conflicting org-toc? Rasmus
2015-04-20 21:06 ` Leo Ufimtsev
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=1565013277.1255423.1429285545379.JavaMail.zimbra@redhat.com \
--to=lufimtse@redhat.com \
--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).