From: Stefan Monnier <monnier@iro.umontreal.ca>
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 13:10:39 -0500 [thread overview]
Message-ID: <jwvr4acfere.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a9h0ie4n.fsf@gmail.com> (Thierry Volpiatto's message of "Tue, 19 Nov 2013 16:51:20 +0100")
> 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!
> `----
Note that this warning is not necessarily a problem. Actually, I tend
to think we should just get rid of this warning (which I added, a few
years ago).
> So I am dropping the support for org-keywords in helm as I don't want to
> reread the whole org.el file.
BTW, why not try to push Helm's support for Org to Org, i.e. make Org
support Helm, rather than the other way around?
I think Helm (and company-mode, auto-complete, ...) should always go in
that direction: provide the infrastructure and then get the various
other modes to use that infrastructure, rather than add separate ad-hoc
glue-code which tends to need to be maintained on the wrong side of
the fence (as seen here).
Stefan
next prev parent reply other threads:[~2013-11-19 18:10 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
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 [this message]
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=jwvr4acfere.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).