possible bug

possible bug

[Pete Phillips]

Evenin' all.  

(for all you UK-based 40-somethings and over, bet that brings back
Saturday night telly! for the rest, it was how "Dixon of Dock Green"
used to introduce the
programme. http://en.wikipedia.org/wiki/Dixon_of_Dock_Green)

I'm having two problems with org-mode.

Problem 1
=========
In org-agenda-custom-commands I have the 's' argument defined as:

 ("s" "SMTL Stuff"
  ((tags "'(time up tags-up)")
   (tags "Office")
   (tags "LaptopS")
   (tags "CAG")
   (tags "Q2")
   (tags "TG")
   (tags "WHS")
   (tags "WaitingS")
   (tags "SometimeS")
   ... bunch of other tags removed .....
   (agenda)))

If I am in my TODO.org file, and have everything collapsed except the
three top level items, and I hit C-c a s, I only get ONE of each tag
specified above displayed in the buffer.  If I hit <Shift><Tab> and
*then* run the command, I get all of the tagged items for each tag. I
can of course get around it by making sure I expand the whole outline
first of all, but suspect it shouldn't work like this.

Problem 2 
========== 

After a while, hitting C-c a s just throws the CPU into 100%
utilisation, and it doesn't come back.  It is interruptable with ^G.
Exiting emacs and starting it again make it work OK.

Trying to make it happen before I send this email, I can't, of course!
However, just before I started writing this email I had to restart emacs
because of just that problem.

I'm using 0rg-mode 4.49 and emacs 22.0.50.1 from CVS.


Regards,
Pete

Possible bug

[Subhan Michael Tindall]

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

I'm not sure if this counts as a bug or not:

If I run a custom agenda (eg. "R") with sticky agendas, it displays in an buffer with the name
*Org Agenda (R)*
If this buffer is then renamed to e.g.
(rename-buffer "*R-Agenda*")
*R-Agenda*
And is then refreshed by hitting r, the agenda is properly rebuilt BUT in a new buffer named *Org Agenda(R)*, resulting in two differing agendas.

Is this appropriate behavior? It seems that rebuilding the agenda should respect the current buffer name. I'm very new at programing for lisp, so I'm not sure I'm using the right functions here.

I've poked around a bit in the code, but my elisp-fu is quite weak. I couldn't find an easy way to pass a buffer name in to org-agenda to be used, nor was it entirely clear to me how to modify org-agenda to grab & respect the buffer name when rebuilding a 'sticky' one.





This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message.  Thank you.

[-- Attachment #2: Type: text/html, Size: 3802 bytes --]

Re: Possible bug

[Nicolas Goaziou]

Hello,

Subhan Michael Tindall <SubhanT@familycareinc.org> writes:

> I'm not sure if this counts as a bug or not:
>
> If I run a custom agenda (eg. "R") with sticky agendas, it displays in an buffer with the name
> *Org Agenda (R)*
> If this buffer is then renamed to e.g.
> (rename-buffer "*R-Agenda*")

Why would you need that?

> *R-Agenda*
> And is then refreshed by hitting r, the agenda is properly rebuilt BUT in a new buffer named *Org Agenda(R)*, resulting in two differing agendas.
>
> Is this appropriate behavior? It seems that rebuilding the agenda
> should respect the current buffer name. I'm very new at programing for
> lisp, so I'm not sure I'm using the right functions here.

IIRC, sticky agenda relies on buffer names to know if agenda needs to be
updated. So, it is not a good idea to rename agenda buffers.


Regards,

-- 
Nicolas Goaziou