From: Bastien <bzg@gnu.org>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bugs in property searches?
Date: Fri, 31 Jan 2014 13:33:58 +0100 [thread overview]
Message-ID: <874n4kjpop.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87r47r74ye.fsf@gmail.com> (Nick Dokos's message of "Wed, 29 Jan 2014 00:05:45 -0500")
Nick Dokos <ndokos@gmail.com> writes:
> OK, I played the git blame game and found commit 3ec38f5c:
I reverted this commit, so this particular bug is fixed*.
Thanks John and Nick,
* I could not remember why I used `save-window-excursion' here.
I should have documented this in the commit message. If anyone
finds out what this was supposed to fix, please let us know.
But `save-window-excursion' is rarely a good choice, so I think
we're good like this.
--
Bastien
prev parent reply other threads:[~2014-01-31 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 2:00 bugs in property searches? John Kitchin
2014-01-29 5:05 ` Nick Dokos
2014-01-31 12:33 ` Bastien [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=874n4kjpop.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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).