Incompatible agenda commands

Incompatible agenda commands

[Sebastien Vauban]

Hello,

While a custom agenda command such as the following used to work some time
ago, it does not anymore.

--8<---------------cut here---------------start------------->8---
  (add-to-list 'org-agenda-custom-commands
               '("D" "Stuck + agenda"
                 ((stuck "")
                  (agenda ""
                          ((org-agenda-span 'week))))) t)
--8<---------------cut here---------------end--------------->8---

Now, it seems that the "stuck" block view inhibits any extra view to be
displayed afterward.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Incompatible agenda commands

[Bastien]

Hi Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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.

Thanks,

-- 
 Bastien

Re: Incompatible agenda commands

[Sebastien Vauban]

Bastien,

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?

Yes, you do understand what I meant.

> If so, I cannot reproduce it.

I hate those!  I'll try to provide you with a reproducible recipe, then.
Thanks for looking at it.

Best regards,
  Seb

-- 
Sebastien Vauban

[bug] Incompatible agenda commands

[Sebastien Vauban]

"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:

--8<---------------cut here---------------start------------->8---
  (setq org-agenda-sticky nil)
--8<---------------cut here---------------end--------------->8---

and you'll be bitten by that bug!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [bug] Incompatible agenda commands

[Bastien]

Hi Sébastien,

"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

>   (setq org-agenda-sticky nil)
>
> and you'll be bitten by that bug!

Still not bitten by this bug :)

-- 
 Bastien

Re: [bug] Incompatible agenda commands

[Bastien]

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

Re: [bug] Incompatible agenda commands

[Matt Lundin]

Bastien <bzg@gnu.org> writes:

> 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?

Unfortunately, I cannot reproduce it either. Both the stuck agenda and
the weekly agenda display on my end. 

Matt

Re: Please confirm your message

[Matt Lundin]

Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org>
writes:

> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> <mdl@imapmail.org> has not been verified.
>
> To release your message for delivery, please send an empty message
> to the following address, or use your mailer's "Reply" feature.
>
>    public-emacs-orgmode-mXXj517/zsQ-confirm-1393852159.12983.21926f@plane.gmane.org
>
> This confirmation verifies that your message is legitimate and not
> junk-mail. You should only have to confirm your address once.
>
> If you do not respond to this confirmation request within 14 days,
> your message will not be delivered.
>
> From: Matt Lundin <mdl@imapmail.org>
> Subject: Re: [bug] Incompatible agenda commands
> To: Bastien <bzg@gnu.org>
> Cc: "Sebastien Vauban" <public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>, public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
> Date: Mon, 03 Mar 2014 07:09:04 -0600 (45 minutes, 53 seconds ago)
> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux)
>
>
> Bastien <bzg@gnu.org> writes:
>
>> 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?
>
> Unfortunately, I cannot reproduce it either. Both the stuck agenda and
> the weekly agenda display on my end. 
>
> Matt
>
>
> ----------

Re: Please confirm your message

[Matt Lundin]

This email resulted from my attempt to reply to an obfuscated email from
the gmane public mailer. I have no idea why it sent my reply to the
list.

As an aside, is there a graceful with these emails in gnus. ( When I do
a wide reply to emails with addresses obfuscated by gmane, I always get
these requests for confirmation.

Matt

Matt Lundin <mdl@imapmail.org> writes:

> Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org>
> writes:
>
>> This message was created automatically by mail delivery software (TMDA).
>>
>> Your message attached below is being held because the address
>> <mdl@imapmail.org> has not been verified.
>>
>> To release your message for delivery, please send an empty message
>> to the following address, or use your mailer's "Reply" feature.
>>
>>    public-emacs-orgmode-mXXj517/zsQ-confirm-1393852159.12983.21926f@plane.gmane.org
>>
>> This confirmation verifies that your message is legitimate and not
>> junk-mail. You should only have to confirm your address once.
>>
>> If you do not respond to this confirmation request within 14 days,
>> your message will not be delivered.
>>
>> From: Matt Lundin <mdl@imapmail.org>
>> Subject: Re: [bug] Incompatible agenda commands
>> To: Bastien <bzg@gnu.org>
>> Cc: "Sebastien Vauban" <public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>, public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
>> Date: Mon, 03 Mar 2014 07:09:04 -0600 (45 minutes, 53 seconds ago)
>> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux)
>>
>>
>> Bastien <bzg@gnu.org> writes:
>>
>>> 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?
>>
>> Unfortunately, I cannot reproduce it either. Both the stuck agenda and
>> the weekly agenda display on my end. 
>>
>> Matt
>>
>>
>> ----------

Re: Please confirm your message

[Matt Lundin]

Matt Lundin <mdl@imapmail.org> writes:

> This email resulted from my attempt to reply to an obfuscated email from
> the gmane public mailer. I have no idea why it sent my reply to the
> list.
>
> As an aside, is there a graceful with these emails in gnus. When I do

Should read: "is there a graceful way to deal with these emails in gnus?"

Matt

Re: [bug] Incompatible agenda commands

[Sebastien Vauban]

Hello Bastien and Matt,

Matt Lundin wrote:
> Bastien <bzg-mXXj517/zsQ@public.gmane.org> writes:
>> Sebastien Vauban 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?
>
> Unfortunately, I cannot reproduce it either. Both the stuck agenda and
> the weekly agenda display on my end.

Sorry, I meant: setting `org-agenda-sticky' to a non-nil value... as nil
is its default value, anyway...

--8<---------------cut here---------------start------------->8---
(require 'org-agenda)

(add-to-list 'org-agenda-custom-commands
             '("D" "Stuck + agenda"
               ((stuck "")
                (agenda ""
                        ((org-agenda-span 'week))))) t)

(setq org-agenda-sticky t)
--8<---------------cut here---------------end--------------->8---

This time (I don't know why I did not see it the other times), I even
see an error message:

--8<---------------cut here---------------start------------->8---
save-current-buffer: No buffer named *Org Agenda(D:+LEVEL=2/-DONE)*
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Please confirm your message

[Denis Bitouzé]

Le 14/09/15 à 08h36, Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org> a écrit :

> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org> has not been verified.
>
> To release your message for delivery, please send an empty message
> to the following address, or use your mailer's "Reply" feature.
>
>    public-emacs-orgmode-mXXj517/zsQ-confirm-1442212612.9320.da9aaf@plane.gmane.org
>
> This confirmation verifies that your message is legitimate and not
> junk-mail. You should only have to confirm your address once.
>
> If you do not respond to this confirmation request within 14 days,
> your message will not be delivered.
>
> From: Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
> Subject: Re: Bug: \vert{} exported to markdown not as expected [8.3.1
> 	(8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
> To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
> Cc: Denis Bitouzé
> 	<public-dbitouze-39ZsbGIQGT5GWvitb5QawA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
> 	public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
> Date: Mon, 14 Sep 2015 08:35:04 +0200 (35 minutes, 18 seconds ago)
>
>
> Le 13/09/15 à 22h47, Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> a écrit :
>
>> Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org> writes:
>>
>>> 1. For _, \under{} is necessary since _ at the org mode level is
>>>    exported as \_.
>>> 2. For |, source | could be okay. But I'd like to use strings as above
>>>    in tables and, AFAIK, the only way to have pipe symbols in a table at
>>>    the org mode level is to code them \vert{}.  And that's the purpose
>>>    of my bug report, \vert{} is exported as &vert;, not as "real" |.
>>>
>>> In other words, I was happy with \under{} that exports real _ and,
>>> IMHO, \vert{} should do the same with |.
>>
>> Markdown export back-end use :html conventions to translate entities.
>> For some reason, HTML prefers &vert; over |, and so does markdown.
>
> &vert; and | are displayed the same way but can have different
> "meanings".
>
>> There are a few options available:
>>
>>   1. Prefer | over &vert; in HTML
>
> Maybe I'm wrong but wouldn't this break backward compatibility?
>
>>   2. Overwrite "vert" entity with a new one that would do 1. So
>>      basically, this is 1 but on your machine only.
>
> The feature I'm requesting may be useful to others.
>
>>   3. Use a new entity that becomes | when used in HTML export.
>
> It would be harmless.
>
>> WDYT?
>
> The 3rd option looks the best one to me.
>
> Regards.
-- 
Denis

Re: Please confirm your message

[Denis Bitouzé]

Le 14/09/15 à 09h12, Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org> a écrit :

> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org> has not been verified.
>
> To release your message for delivery, please send an empty message
> to the following address, or use your mailer's "Reply" feature.
>
>    public-emacs-orgmode-mXXj517/zsQ-confirm-1442214744.28220.0d5b6f@plane.gmane.org
>
> This confirmation verifies that your message is legitimate and not
> junk-mail. You should only have to confirm your address once.
>
> If you do not respond to this confirmation request within 14 days,
> your message will not be delivered.
>
> From: Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
> Subject: Re: Please confirm your message
> To: Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
> Cc: public-emacs-orgmode-mXXj517/zsQ-confirm-1442212612.9320.da9aaf@plane.gmane.org
> Date: Mon, 14 Sep 2015 09:10:40 +0200 (1 minute, 2 seconds ago)
>
>
> Le 14/09/15 à 08h36, Gmane Remailer <public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org> a écrit :
>
>> This message was created automatically by mail delivery software (TMDA).
>>
>> Your message attached below is being held because the address
>> <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org> has not been verified.
>>
>> To release your message for delivery, please send an empty message
>> to the following address, or use your mailer's "Reply" feature.
>>
>>    public-emacs-orgmode-mXXj517/zsQ-confirm-1442212612.9320.da9aaf@plane.gmane.org
>>
>> This confirmation verifies that your message is legitimate and not
>> junk-mail. You should only have to confirm your address once.
>>
>> If you do not respond to this confirmation request within 14 days,
>> your message will not be delivered.
>>
>> From: Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
>> Subject: Re: Bug: \vert{} exported to markdown not as expected [8.3.1
>> 	(8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
>> To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
>> Cc: Denis Bitouzé
>> 	<public-dbitouze-39ZsbGIQGT5GWvitb5QawA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
>> 	public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
>> Date: Mon, 14 Sep 2015 08:35:04 +0200 (35 minutes, 18 seconds ago)
>>
>>
>> Le 13/09/15 à 22h47, Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> a écrit :
>>
>>> Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org> writes:
>>>
>>>> 1. For _, \under{} is necessary since _ at the org mode level is
>>>>    exported as \_.
>>>> 2. For |, source | could be okay. But I'd like to use strings as above
>>>>    in tables and, AFAIK, the only way to have pipe symbols in a table at
>>>>    the org mode level is to code them \vert{}.  And that's the purpose
>>>>    of my bug report, \vert{} is exported as &vert;, not as "real" |.
>>>>
>>>> In other words, I was happy with \under{} that exports real _ and,
>>>> IMHO, \vert{} should do the same with |.
>>>
>>> Markdown export back-end use :html conventions to translate entities.
>>> For some reason, HTML prefers &vert; over |, and so does markdown.
>>
>> &vert; and | are displayed the same way but can have different
>> "meanings".
>>
>>> There are a few options available:
>>>
>>>   1. Prefer | over &vert; in HTML
>>
>> Maybe I'm wrong but wouldn't this break backward compatibility?
>>
>>>   2. Overwrite "vert" entity with a new one that would do 1. So
>>>      basically, this is 1 but on your machine only.
>>
>> The feature I'm requesting may be useful to others.
>>
>>>   3. Use a new entity that becomes | when used in HTML export.
>>
>> It would be harmless.
>>
>>> WDYT?
>>
>> The 3rd option looks the best one to me.
>>
>> Regards.
-- 
Denis