From: Dave Abrahams <email@example.com>
To: David Maus <firstname.lastname@example.org>
Subject: Re: Bug: [patch] Fixes behavior of org-agenda-tree-to-indirect-buffer [7.8.02 (release_7.7.796.gc512)]
Date: Sat, 25 Feb 2012 14:43:13 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Dave Abrahams's message of "Sat, 25 Feb 2012 08:34:22 -0500")
on Sat Feb 25 2012, Dave Abrahams <dave-AT-boostpro.com> wrote:
> on Sat Feb 25 2012, David Maus <dmaus-AT-ictsoc.de> wrote:
>> Hi Dave,
>> At Fri, 17 Feb 2012 22:48:13 -1000,
>> Dave Abrahams wrote:
>>> [1 <text/plain (7bit)>]
>>> Remember to cover the basics, that is, what you expected to happen and
>>> what in fact did happen. You don't know how to make a good report? See
>>> Your bug report will be posted to the Org-mode mailing list.
>>> This function was misbehaving in a number of ways. The enclosed patch
>>> represents the changes necessary to make it work properly, accumulated
>>> over several weeks of testing. Sorry if the description is a bit vague.
>> Thanks for the patch. I implemented the first to modifications (handle
>> org-last-indirect-buffer being nil and window-live-p
> Sorry, I can't parse that last sentence, and as a result I'm having
> trouble understanding the rest of the message.
>> These were indeed bugs or glitches.
>> The third modification (set visibility according to property) is a new
>> feature. Currently org-tree-to-indirect buffer does not use the
>> VISIBILITY property but it makes sense to me to do so.
Well, new feature or not, org-tree-to-indirect-buffer stopped behaving
correctly for me when it was added, and I had to make adjustments.
>> I'll check this out and see to implement this.
prev parent reply other threads:[~2012-02-25 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 8:48 Bug: [patch] Fixes behavior of org-agenda-tree-to-indirect-buffer [7.8.02 (release_7.7.796.gc512)] Dave Abrahams
2012-02-25 10:26 ` David Maus
2012-02-25 13:34 ` Dave Abrahams
2012-02-25 15:55 ` David Maus
2012-02-25 19:43 ` Dave Abrahams [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).