From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [bug] Incompatible agenda commands
Date: Mon, 03 Mar 2014 13:33:35 +0100 [thread overview]
Message-ID: <87d2i3cvhc.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86txbvduxm.fsf_-_@somewhere.org> (Sebastien Vauban's message of "Wed, 19 Feb 2014 15:43:49 +0100")
Hi Sébastien,
"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> "Sebastien Vauban" wrote:
>> Bastien wrote:
>>> "Sebastien Vauban" writes:
>>>
>>>> While a custom agenda command such as the following used to work some time
>>>> ago, it does not anymore.
>>>>
>>>> (add-to-list 'org-agenda-custom-commands
>>>> '("D" "Stuck + agenda"
>>>> ((stuck "")
>>>> (agenda ""
>>>> ((org-agenda-span 'week))))) t)
>>>>
>>>> Now, it seems that the "stuck" block view inhibits any extra view to be
>>>> displayed afterward.
>>>
>>> do I understand correctly that you only get the stuck view and not the
>>> agenda view? If so, I cannot reproduce it.
>>
>> I'll try to provide you with a reproducible recipe, then.
>
> Add the following line to this ECM:
>
> (setq org-agenda-sticky nil)
>
> and you'll be bitten by that bug!
Mhh... still can't reproduce the bug. Anyone else?
--
Bastien
next prev parent reply other threads:[~2014-03-03 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:56 Incompatible agenda commands Sebastien Vauban
2013-04-04 9:50 ` Bastien
2013-04-04 21:07 ` Sebastien Vauban
2014-02-19 14:43 ` [bug] " Sebastien Vauban
2014-03-01 8:19 ` Bastien
2014-03-03 12:33 ` Bastien [this message]
2014-03-03 13:09 ` Matt Lundin
[not found] ` <1393852160.12983.TMDA@plane.gmane.org>
2014-03-03 13:55 ` Please confirm your message Matt Lundin
2014-03-03 14:07 ` Matt Lundin
2014-03-03 14:10 ` Matt Lundin
2014-03-11 14:44 ` [bug] Incompatible agenda commands Sebastien Vauban
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=87d2i3cvhc.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \
/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).