From: Bastien <bzg@gnu.org>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: org-crypt bug and other org inconveniences.
Date: Tue, 19 Nov 2013 17:41:02 +0100 [thread overview]
Message-ID: <87bo1guyxt.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87a9h0ie4n.fsf@gmail.com> (Thierry Volpiatto's message of "Tue, 19 Nov 2013 16:51:20 +0100")
Hi Thierry,
Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
> I sent a bug about org-crypt months ago (with patch to fix it).
> I see org have been merged into trunk and the bug is still here...
>
> ,----
> | Making epg-context local to *epg* while let-bound!
> `----
Yes, your message is here:
http://article.gmane.org/gmane.emacs.bugs/77307
I wasn't sure what I could do about it and I'm not Org
maintainer anymore.
I recommend you send this bug reports to the Org-mode list
directly, that's the best way to get a quick reply.
> Also functions/vars have been removed without infos on how to replace
> them.
>
> At least `org-additional-option-like-keywords' and
> `org-get-current-options'.
This is in the Emacs Changelog:
* org.el (org-additional-option-like-keywords): Remove variable.
(org-get-export-keywords): New function.
(org-options-keywords): Update default list of keywords.
* org-macs.el (org-default-options): Rename and adapt from
`org-get-current-options'.
You need to use `org-options-keywords' and `org-default-options'.
> So I am dropping the support for org-keywords in helm as I don't want to
> reread the whole org.el file.
Please read etc/ORG-NEWS and lisp/org/ChangeLog for such informations
and let me know if I can help.
--
Bastien
next prev parent reply other threads:[~2013-11-19 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 15:51 org-crypt bug and other org inconveniences Thierry Volpiatto
2013-11-19 16:41 ` Bastien [this message]
2013-11-20 7:32 ` Thierry Volpiatto
2013-11-21 8:31 ` Thierry Volpiatto
2013-11-21 9:07 ` Bastien
2013-11-19 18:10 ` Stefan Monnier
2013-11-20 7:45 ` Thierry Volpiatto
2013-11-20 13:44 ` Stefan Monnier
2013-11-20 14:20 ` Thierry Volpiatto
2013-11-20 18:29 ` Bastien
2013-11-20 18:30 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bo1guyxt.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@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.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).