From: Samuel Wales <samologist@gmail.com>
To: Manuel Hermenegildo <herme@fi.upm.es>
Cc: Org Mode List <emacs-orgmode@gnu.org>,
"Dominik, Carsten" <C.Dominik@uva.nl>
Subject: Re: Sticky Agenda buffer: Announcement and request for testing
Date: Tue, 13 Mar 2012 12:21:47 -0700 [thread overview]
Message-ID: <CAJcAo8sMVmnacVn+BBm=fyxtFw2jCCA1KNMVFXeTamQ0Ai7NRg@mail.gmail.com> (raw)
In-Reply-To: <20319.33874.900923.628931@gazelle.local>
Cannot test at this time, but I have an a priori comment.
Having multiple agenda buffers around increases the probability that
you will change the outline buffers before you perform an operation in
the agenda. You might do this either by performing agenda commands in
an agenda buffer or by directly editing the outline buffer.
As the agenda uses markers to get to the outline buffer, this
increases the probability that you will perform an operation that will
corrupt the outline buffer.
I have not thought about this deeply, but perhaps every agenda command
should perform a rudimentary check, if possible, to make sure the
marker still points to where it did when the agenda in which it was
called was created.
This might entail storing header strings, or the like. It might not be ideal.
However, I have noticed buffer corruption in the past and I think it
would be good to keep this risk in mind in case we can come up with
ways of making agenda commands safer.
I avoid using the agenda because I don't always know if the marker
still points where it should.
Hope this helps.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2012-03-13 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 12:48 Sticky Agenda buffer: Announcement and request for testing Dominik, Carsten
2012-03-13 17:30 ` Manuel Hermenegildo
2012-03-13 19:21 ` Samuel Wales [this message]
2012-04-03 5:37 ` Bastien
2012-03-14 15:54 ` Rainer Stengele
2012-03-14 18:12 ` Max Mikhanosha
2012-03-22 9:57 ` Rainer Stengele
2012-03-22 10:12 ` Bastien
2012-03-22 11:04 ` Rainer Stengele
2012-03-27 11:46 ` Martyn Jago
2012-04-03 5:33 ` Bastien
2012-04-03 6:58 ` Carsten Dominik
2012-04-03 7:06 ` Bastien
2012-04-03 7:09 ` Dominik, Carsten
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='CAJcAo8sMVmnacVn+BBm=fyxtFw2jCCA1KNMVFXeTamQ0Ai7NRg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=C.Dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=herme@fi.upm.es \
/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).