Re: [O] org-agenda-todo obliterates my windows

2019-08-29 Thread Phil Regier
Well, that sure was easy, and I certainly had missed it.  This selection
does indeed produce the behavior I was hoping for; thanks so much for the
help!

PR

On Thu, Aug 29, 2019 at 12:17 PM Jack Kamm  wrote:

> > Is there any way to just open my org-agenda-todo items in the /current/
> > window, or even just any window that already happens to be open, without
> > modifying, splitting, or above all deleting any others?
>
> Does customizing the variable org-agenda-window-setup (e.g. by setting
> it to 'current-window) solve this?
>


Re: [O] org-agenda-todo obliterates my windows

2019-08-29 Thread Jack Kamm
> Is there any way to just open my org-agenda-todo items in the /current/
> window, or even just any window that already happens to be open, without
> modifying, splitting, or above all deleting any others?

Does customizing the variable org-agenda-window-setup (e.g. by setting
it to 'current-window) solve this?



[O] org-agenda-todo obliterates my windows

2019-08-29 Thread Phil Regier
I've been ignoring this for a long time, but it's getting more disruptive
as more of my daily life lives in emacs/org; I've tried a little blind
hacking and only managed to make things worse, and I feel like I'm missing
something easy and obvious.

Is there any way to just open my org-agenda-todo items in the /current/
window, or even just any window that already happens to be open, without
modifying, splitting, or above all deleting any others?

Sorry if this has been discussed already; I tried searching my list folder
(and admit I don't do a good job of following the list in the first place)
but keep coming up empty.


Re: [O] org-agenda list on other language than english

2019-08-11 Thread andrés ramírez
Hi Thomas.

Thomas> Localised day and month names are taken from your (apparently
Thomas> missing) calendar setup.  Make sure that your startup file
Thomas> setq's at least these two variables:

Thomas> - calendar-month-name-array - calendar-day-name-array (starts
Thomas> with $SUNDAY)

Thomas> Also, it might be advisable to set calendar-date-style (to
Thomas> 'european in my case).

Thanks. That was what I was looking for.

Best Regards



Re: [O] org-agenda list on other language than english

2019-08-11 Thread Thomas Plass
Hello,

Andrés Ramírez wrote at 14:30 on August 10, 2019:
: 
: Would it be possibe to render agenda in other language than English.

Mostly.

Localised day and month names are taken from your (apparently missing)
calendar setup.  Make sure that your startup file setq's at least
these two variables:

- calendar-month-name-array
- calendar-day-name-array (starts with $SUNDAY)

Also, it might be advisable to set calendar-date-style (to 'european
in my case).

My setup for German is this, modify for Spanish as appropriate:

(setq calendar-date-style 'european
  calendar-month-name-array ["Januar" "Februar" "März" "April" "Mai" "Juni"
 "Juli" "August" "September" "Oktober" 
"November" "Dezember"]
  calendar-day-name-array ["Sonntag" "Montag" "Dienstag" "Mittwoch"
   "Donnerstag" "Freitag" "Samstag"]
   )

The "days" in "10 days-agenda", however, is hard-wired.

: Convert from this:
: --8<---cut here---start->8---
: 10 days-agenda (W32-W33):
: Wednesday   7 August 2019
: 
: To this (Spanish):
: --8<---cut here---start->8---
: 10 dias-agenda (W32-W33):
: Miercoles   7 Agosto 2019

Regards

Thomas



[O] org-agenda list on other language than english

2019-08-10 Thread Andrés Ramírez
Hi.

Would it be possibe to render agenda in other language than English.

Convert from this:
--8<---cut here---start->8---
10 days-agenda (W32-W33):
Wednesday   7 August 2019
Thursday8 August 2019
Friday  9 August 2019
Saturday   10 August 2019
Sunday 11 August 2019
Monday 12 August 2019 W33
Tuesday13 August 2019
Wednesday  14 August 2019
Thursday   15 August 2019
Friday 16 August 2019
--8<---cut here---end--->8---

To this (Spanish):
--8<---cut here---start->8---
10 dias-agenda (W32-W33):
Miercoles   7 Agosto 2019
Jueves  8 Agosto 2019
Viernes 9 Agosto 2019
Sabado 10 Agosto 2019
Domingo11 Agosto 2019
Lunes  12 Agosto 2019 W33
Martes 13 Agosto 2019
Miercoles  14 Agosto 2019
Jueves 15 Agosto 2019
Viernes16 Agosto 2019
--8<---cut here---end--->8---

If that is not implemented. Any suggestions where could I do the replacements?.

BR



[O] Org-agenda and error in tags position

2019-05-16 Thread leo

Hi! I write because I am experiencing a problem with org agenda and
more precisely with the positioning of the tags which as can be seen
from the screenshot are always displayed on a new line (while I expect
them to be displayed to the right of the task).
It only happens with org-agenda. In .org files the display is correct

The problem is with Org 9.2.3 and Emacs 26.1 on xubuntu 19.04.

Here a screenshot of how the org-agenda view appears:
https://share.riseup.net/#E1pz3vlYKm27KKTSTQE6qg

I also tried a new .emacs configuration but nothing changes.

Here the part of my configuration concerning org agenda:
https://pad.riseup.net/p/Nv-AnovgxUkUlXwz3HzC

I researched but did not find similar situations and a solution on the
web.

Can you
give me a hand?

Thanks a lot,

--
leo



[O] org-agenda-sorting-strategy deadline-up behavior with no deadline

2019-04-23 Thread Jake Vossen
I am fairly new to emacs, so my apologies if this is a simple question,
however, I really cannot seem to figure out what I am doing wrong here.

I am trying to sort my agenda deadlines by the soonest due date first,
so I have set org-agenda-sorting-strategy to deadline-up. However, items
with no due date appear before items with a due date, where I wish they
would appear after. Anyone have any ideas?

Thank you!


signature.asc
Description: PGP signature


[O] org-agenda-custom-commands and org-publish

2019-03-27 Thread David Masterson
Is it possible to mix generating (say) a monthly agenda into the
publishing action?  That is, when I generate my website via org-publish,
I'd like to include in it the current agenda for the next month as
another HTML page.  Can that be done?

--
David



Re: [O] org-agenda fails when a scheduled/deadline date is in the past [9.1.9 (release_9.1.9-65-g5e4542 @ /Users/borwick/.emacs.d/elpa/org-plus-contrib-20190218/)]

2019-02-20 Thread Nicolas Goaziou
Hello,

John Borwick  writes:

> Hello! OK I just downloaded & installed org-plus-contrib-20190218.tar.
> Unfortunately I still got this error. The last working version for me
> is org-plus-contrib-20181224.tar.

I cannot reproduce it. Maybe a mixed installation?

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-log-mode omits some items from LOGBOOK drawers

2019-01-16 Thread Samuel Wales
hi,

On 1/16/19, N. Jackson  wrote:
>
> In Org Agenda, `C-u l', which IIUC is supposed to "show all possible
> log items, not only the ones configured in
> `org-agenda-log-mode-items'" shows clocking of work, closing of
> entries, and other state changes of entries (tagged in the agenda
> with "Clocked", "Closed", and "State" respectively).
>
> That is very useful. However, note entries in the LOGBOOK drawer
> (created with org-add-note) are unfortunately omitted.

notes don't have special status afaik.  therefore, they will not show
unless inactive ts show.  they include inactive ts.

so to show them you show inactive.  more below.

btw inactive ts has a special definition in org:

the closed planning line tagged ts includes an inactive ts, but it is
a planning line ts, so it is not considered an inactive ts in some
contexts.  it is considered a closed ts in those contexts.  for
example, when getting an inactive ts property.  you will not get the
inactive ts in closed ts.

in those contexts, and in most of org, inactive means bare inactive.
which i think is reasonable.

in contrast, state, as pointed out recently on the list, is not really
recognized by org.  except as a log mode item.  which is only partly
recognized.

any inactive ts in it are considered inactive ts, unlike with closed.

thus, if you turn on inactive ts, you will have to remove state from
the log mode items to avoid duplication.  this will look slightly
different in the agenda [you don't get the state indication].  but to
me that's no big deal.

you can keep closed, because that will not duplicate.

>
> Also, all my LOGBOOK drawers contain a CREATED inactive time stamp
> (placed there by my capture templates), but these CREATED entries
> are also omitted.

because they are inactive and inactive do not show [until you do what
i suggest below].

so all possible doesn't really mean all possible.  you have to catch
the tone of voice :].

this possibly dates back to when org didn't really have a concept of
inactive ts.

>
> Am I doing something wrong? Are these other entries from the LOGBOOK
> drawer expected to be included in the Agenda with `C-u l' -- I
> realise that "all possible log items" is not the same as "all log
> items", but it isn't clear why it wouldn't be possible!

inconsistencies in log mode.

you need to turn on inactive.

we sort of have at least 3 levels of log mode: regular/custom, all,
and "no i really mean all so let's include inactive and fix the
inconsistencies caused by doing so".

also there is a quasi-level implied by skip variables [see below].  so
4 levels of log mode.

the ones i find useful are nothing logged at all, or "everything no i
mean really everything" logged.  so for me i only need 2 levels of log
mode.

the command to toggle showing inactive is overloaded with query items.
so i don't really recommend it unless it works for you.

it is not persistent.

i recommend making a command that toggles
org-agenda-include-inactive-timestamps.  this is a defvar.  it works.
it is used by the overloaded command also.

i also have that variable toggled at the same time that log mode gets
toggled, using defadvice.  for health reasons i can't do more than
very very very trivial debugging and coding, so i cannot check if i've
figured it out completely enough.  i think i have, when i wrote it
long ago, modulo the skip if variables issue mentioned above.

in principle it might be better to have inactive timestamps turned on
or off at agenda creation time depending on the value of whatever
variable indicates that log mode is on.  then it will still work with
both values of start with log mode.

[unless somebody wants to fix it so that org does tihs automatically.]

>
>
>
>
>

the skip variables [like sckip-whatever-if-done] will either show
entries both as logged and as done, or as neither.  this means that if
you set them to non-nil so that they do not annoy you in your regular
agenda, they will silently be omitted in log mode.  you might not
notice this omission if they are not a common type of ts for you.

nicolas has indicated that he will not fix this one, but that others
are welcome to.  fixing it will bring us toward a more consistent log
mode.

tldr: toggle that defvar to get what you want, then remove state from
your log mode items list.  and make sure you do not set any of the
skip if variables to non-nil.

there's probably a more involved workaround where there is some
intermediate list of tasks for the agenda that you can winnow
duplicates from, but i am not able to do it.  and i think the above
might owrk for you.  and somebody might fix the inconsistencies
anyway.

hope that helps at least a bit.

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---

[O] org-agenda-log-mode omits some items from LOGBOOK drawers

2019-01-16 Thread N. Jackson


In Org Agenda, `C-u l', which IIUC is supposed to "show all possible
log items, not only the ones configured in
`org-agenda-log-mode-items'" shows clocking of work, closing of
entries, and other state changes of entries (tagged in the agenda
with "Clocked", "Closed", and "State" respectively).

That is very useful. However, note entries in the LOGBOOK drawer
(created with org-add-note) are unfortunately omitted.

Also, all my LOGBOOK drawers contain a CREATED inactive time stamp
(placed there by my capture templates), but these CREATED entries
are also omitted.

Am I doing something wrong? Are these other entries from the LOGBOOK
drawer expected to be included in the Agenda with `C-u l' -- I
realise that "all possible log items" is not the same as "all log
items", but it isn't clear why it wouldn't be possible!






Re: [O] Org agenda started behaving badly

2018-06-14 Thread Marcin Borkowski


On 2018-06-11, at 21:06, Nick Dokos  wrote:

> Marcin Borkowski  writes:
>
>> Hi all,
>>
>> so out of nowhere my org agenda started behaving in a strange way.  It
>> seems not to respect my TODO-keywords settings:
>>
>> (setq org-todo-keywords
>>   '((sequence "TODO(t!)" "DONE(d!)")
>>  (sequence "SOMEDAY(s!)")
>>  (sequence "CANCELLED(c@)")
>>  (sequence "WAIT(w!)" "|")))
>>
>> i.e., it now shows all the "CANCELLED" items as if "CANCELLED" was not
>> a todo keyword at all.  When I visit the offending file and issue M-x
>> normal-mode, everything is back to normal again.
>
> What does C-h v org-todo-keywords RET say when you see the problem? Is
> it possible that there is a local variable shadowing the global setting?

Thanks, but I found the culprit.  I was visiting my Org files (in my
init.el, I have e.g. this: (org-agenda-prepare-buffers
(org-agenda-files))) _before_ setting org-todo-keywords...  Stupid
mistake, sorry for the noise.

Best,

--
Marcin Borkowski
http://mbork.pl



Re: [O] Org agenda started behaving badly

2018-06-11 Thread Nick Dokos
Marcin Borkowski  writes:

> Hi all,
>
> so out of nowhere my org agenda started behaving in a strange way.  It
> seems not to respect my TODO-keywords settings:
>
> (setq org-todo-keywords
>   '((sequence "TODO(t!)" "DONE(d!)")
>   (sequence "SOMEDAY(s!)")
>   (sequence "CANCELLED(c@)")
>   (sequence "WAIT(w!)" "|")))
>
> i.e., it now shows all the "CANCELLED" items as if "CANCELLED" was not
> a todo keyword at all.  When I visit the offending file and issue M-x
> normal-mode, everything is back to normal again.
>

What does C-h v org-todo-keywords RET say when you see the problem? Is
it possible that there is a local variable shadowing the global setting?

> Now the strange thing is, I haven't updated Org in a while.  I did now,
> but the problem persists.  I am on
>
> Org mode version 9.1.13 (release_9.1.13-791-g842002 @ [...])
>
> and
>
> GNU Emacs 27.0.50 (commit f1e65b7)
>
> I also can't remember changing my config (but it's quite possible that
> I'm forgetting something).
>
> What I did do is I updated some packages through the Emacs package
> manager, but I don't think this is related.
>
> Now I know this is a bit vague, but does anyone have any idea what might
> cause this, or how I could try to debug this problem?
>
> Of course, I have a lot of Org-mode-related customizations in my
> init.el, but I don't think they are related.  If I'm wrong, I can post
> them here, of course.
>
> Best,
>
> --
> Marcin Borkowski
> http://mbork.pl
>
>

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




[O] Org agenda started behaving badly

2018-06-08 Thread Marcin Borkowski
Hi all,

so out of nowhere my org agenda started behaving in a strange way.  It
seems not to respect my TODO-keywords settings:

--8<---cut here---start->8---
(setq org-todo-keywords
  '((sequence "TODO(t!)" "DONE(d!)")
(sequence "SOMEDAY(s!)")
(sequence "CANCELLED(c@)")
(sequence "WAIT(w!)" "|")))
--8<---cut here---end--->8---

i.e., it now shows all the "CANCELLED" items as if "CANCELLED" was not
a todo keyword at all.  When I visit the offending file and issue M-x
normal-mode, everything is back to normal again.

Now the strange thing is, I haven't updated Org in a while.  I did now,
but the problem persists.  I am on

Org mode version 9.1.13 (release_9.1.13-791-g842002 @ [...])

and

GNU Emacs 27.0.50 (commit f1e65b7)

I also can't remember changing my config (but it's quite possible that
I'm forgetting something).

What I did do is I updated some packages through the Emacs package
manager, but I don't think this is related.

Now I know this is a bit vague, but does anyone have any idea what might
cause this, or how I could try to debug this problem?

Of course, I have a lot of Org-mode-related customizations in my
init.el, but I don't think they are related.  If I'm wrong, I can post
them here, of course.

Best,

--
Marcin Borkowski
http://mbork.pl



Re: [O] Org agenda

2018-01-07 Thread Eric S Fraga
On Saturday,  6 Jan 2018 at 14:13, M. P. wrote:
> I create a TODO and save the file but I can’t see the todo when I
> select todo view in agenda? What am I doing wrong?

Ignore my previous response.  I misread your email.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature


Re: [O] Org agenda

2018-01-07 Thread Eric S Fraga
On Saturday,  6 Jan 2018 at 14:13, M. P. wrote:
> I create a TODO and save the file but I can’t see the todo when I
> select todo view in agenda? What am I doing wrong?

TODO items without schedule or deadline will not appear in the default
agenda view.  Did you schedule the TODO?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6


signature.asc
Description: PGP signature


Re: [O] Org agenda

2018-01-06 Thread Brett Viren
"M. P."  writes:

> I create a TODO and save the file but I can’t see the todo when I
> select todo view in agenda? What am I doing wrong?

Maybe your file is not in the org-agenda-files list.  If so, a quick
check is to visit the file and do "C-c [" (org-agenda-file-to-front).
Then, recheck your agenda todo view.

-Brett.


signature.asc
Description: PGP signature


[O] Org agenda

2018-01-06 Thread M. P.
I create a TODO and save the file but I can’t see the todo when I select todo 
view in agenda? What am I doing wrong?


Re: [O] org-agenda-skip-function does not find inherited tags

2017-09-11 Thread Kaushal Modi
On Wed, Sep 6, 2017 at 12:33 PM Nicolas Goaziou 
wrote:

> You write a more appropriate function and use it as
> `org-agenda-skip-function'. It could re-use the following snippet:
>
>   (not (member "@work" (org-split-string (org-entry-get (point)
> "ALLTAGS"
>

TIL about ALLTAGS and other Special Properties.

That org-split-string though needs the separator argument though, right?

(org-split-string (org-entry-get (point) "ALLTAGS") ":")
-- 

Kaushal Modi


Re: [O] org-agenda-skip-function does not find inherited tags

2017-09-10 Thread Adrian Bradd
Thanks for the pointers. This is what I came up with:

(defun abradd-agenda-tags-inherited (tags)
  (let (beg end m)
(org-back-to-heading t)
(setq beg (point)
  end (progn (outline-next-heading) (1- (point
(goto-char beg)
(and
  (not (member tags (org-get-tags-at)))
  end)))

I copied mostly from org-agenda-skip-if. It isn't very versatile, but works
for now.

On 9 September 2017 at 01:36, Adam Porter  wrote:

> I think the function org-get-tags-at should also be helpful here.
>
>
>


Re: [O] org-agenda-skip-function does not find inherited tags

2017-09-08 Thread Adam Porter
I think the function org-get-tags-at should also be helpful here.




Re: [O] org-agenda-current-time-string partly fontified with emphasis

2017-09-08 Thread Nicolas Goaziou
Hello,

Samuel Wales  writes:

>> You may be able to tweak fontification to ignore this special case. See
>> `org-font-lock-set-keywords-hook' to install a special rule for.
>
> are there examples of the usage of this?

There is one in "contrib/lisp/org-wikinodes.el".

>> It will work as long as you don't export the document. For that case,
>> you could write a filter turning multiple "=" into "\equal".
>
> is there a filter that will change instances /before/ they get
> converted by a backend?

There are two of them: `org-export-before-processing-hook' and
`org-export-before-parsing-hook'.

> i don't want to use hyphens, and org's separator is page-wide.

It depends on the export back-end. You can control the width of the
separator in "latex" and "ascii" back-ends.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-current-time-string partly fontified with emphasis

2017-09-07 Thread Samuel Wales
On 9/7/17, Nicolas Goaziou  wrote:
> Indeed. === really means "=" character in verbatim markup.

fyi but not in all of the agenda current time string.  just the first
part in my example.

> You may be able to tweak fontification to ignore this special case. See
> `org-font-lock-set-keywords-hook' to install a special rule for.

are there examples of the usage of this?

> It will work as long as you don't export the document. For that case,
> you could write a filter turning multiple "=" into "\equal".

is there a filter that will change instances /before/ they get
converted by a backend?  depending on the backend sometimes i want ===
and sometimes a suitable short centered separator.  i don't want to
use hyphens, and org's separator is page-wide.



Re: [O] org-agenda-current-time-string partly fontified with emphasis

2017-09-07 Thread Nicolas Goaziou
Hello,

Samuel Wales  writes:

> On 9/6/17, Samuel Wales  wrote:
>> in the new release, org-agenda-current-time-string is partly fontified
>> if it contains emphasis like "=== test ===".  my guess is best to not
>> fontify as it is not possible to
>> fix unless you turn it off for the entire buffer.
>
> the above is correct, but the cause is possibly related to the fact
> that there is an emphasis change from 9.0.
>
> before, "===" in the outline would not be fontified.  now it is.

Indeed. === really means "=" character in verbatim markup.

> can this be turned off?

You may be able to tweak fontification to ignore this special case. See
`org-font-lock-set-keywords-hook' to install a special rule for.

It will work as long as you don't export the document. For that case,
you could write a filter turning multiple "=" into "\equal".

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-current-time-string partly fontified with emphasis

2017-09-06 Thread Samuel Wales
On 9/6/17, Samuel Wales  wrote:
> in the new release, org-agenda-current-time-string is partly fontified
> if it contains emphasis like "=== test ===".  my guess is best to not
> fontify as it is not possible to
> fix unless you turn it off for the entire buffer.

the above is correct, but the cause is possibly related to the fact
that there is an emphasis change from 9.0.

before, "===" in the outline would not be fontified.  now it is.

can this be turned off?  i use "===" specifically in the outline and
would prefer it in a default font, while preserving =this emphasis=.



[O] org-agenda-current-time-string partly fontified with emphasis

2017-09-06 Thread Samuel Wales
in the new release, org-agenda-current-time-string is partly fontified
if it contains emphasis like "=== test ===".  my guess is best to not
fontify as it is not possible to
fix unless you turn it off for the entire buffer.

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.



Re: [O] org-agenda-skip-function does not find inherited tags

2017-09-06 Thread Nicolas Goaziou
Hello,

Adrian Bradd  writes:

> I have the following custom agenda command:
>
> (setq org-agenda-custom-commands
>   '(("ww" "Work 2 day view"
>  ((agenda ""
>((org-agenda-files '("~/tmp/tmp.org"))
> (org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp
> ":@work:"))
> (org-agenda-start-on-weekday nil)
> (org-agenda-span 2)
> (org-agenda-overriding-header "\n2 day work
> view\n-\n")))
>
> Given the sample file below:
>
> * Top heading with tags
> :@work:admin:
> ** Next heading (inherited tags)
>SCHEDULED: <2017-09-04 Mon>
> ** Next heading (explicit tags)
> :@work:admin:
>SCHEDULED: <2017-09-04 Mon>
>
> The agenda will only display headings that have the tag explicitly defined.
> In this case, "Next heading (explicit tags)".
>
> Is there a way I can convince the agenda to honour inherited tags in this
> case?

You write a more appropriate function and use it as
`org-agenda-skip-function'. It could re-use the following snippet:

  (not (member "@work" (org-split-string (org-entry-get (point) "ALLTAGS"


Regards,

-- 
Nicolas Goaziou



[O] org-agenda-skip-function does not find inherited tags

2017-09-04 Thread Adrian Bradd
Hello,

I have the following custom agenda command:

(setq org-agenda-custom-commands
  '(("ww" "Work 2 day view"
 ((agenda ""
   ((org-agenda-files '("~/tmp/tmp.org"))
(org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp
":@work:"))
(org-agenda-start-on-weekday nil)
(org-agenda-span 2)
(org-agenda-overriding-header "\n2 day work
view\n-\n")))

Given the sample file below:

* Top heading with tags
:@work:admin:
** Next heading (inherited tags)
   SCHEDULED: <2017-09-04 Mon>
** Next heading (explicit tags)
:@work:admin:
   SCHEDULED: <2017-09-04 Mon>

The agenda will only display headings that have the tag explicitly defined.
In this case, "Next heading (explicit tags)".

Is there a way I can convince the agenda to honour inherited tags in this
case?

Cheers,

Adrian


Re: [O] org-agenda time grid broken ?

2017-08-06 Thread Nicolas Goaziou
Hello,

Julien Cubizolles  writes:

> Nicolas Goaziou  writes:
>
>> Hello,
>>
>> Julien Cubizolles  writes:
>>
>>> Did I miss an important change to the way org-agenda-files is to be
>>> used ?
>>
>> It is probably related to the change in `org-agenda-time-grid'. See new
>> docstring.
>
> I've looked into it but the example I provided is run from emacs -Q and
> no change to the default value of org-agenda-time-grid, set to
>
> ((daily today require-timed)
>  (800 1000 1200 1400 1600 1800 2000)
>  ".." "")

I can reproduce it. It looks like the bug reported at
.
>
> Also, I noticed two other things:
>
> * when I'm using org from the git repo, a call to org-agenda throws this
>   error:
>
>   --8<---cut here---start->8---
>   org-agenda-format-item: Symbol’s function definition is void: 
> org-duration-to-minutes
>   --8<---cut here---end--->8---

Something is wrong in your set-up. `org-duration-to-minutes' was
introduced in master.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda time grid broken ?

2017-08-06 Thread Julien Cubizolles
Nicolas Goaziou  writes:

> Hello,
>
> Julien Cubizolles  writes:
>
>> Did I miss an important change to the way org-agenda-files is to be
>> used ?
>
> It is probably related to the change in `org-agenda-time-grid'. See new
> docstring.

I've looked into it but the example I provided is run from emacs -Q and
no change to the default value of org-agenda-time-grid, set to

((daily today require-timed)
 (800 1000 1200 1400 1600 1800 2000)
 ".." "")

Also, I noticed two other things:

* when I'm using org from the git repo, a call to org-agenda throws this
  error:

  --8<---cut here---start->8---
  org-agenda-format-item: Symbol’s function definition is void: 
org-duration-to-minutes
  --8<---cut here---end--->8---

* I'm using
  --8<---cut here---start->8---
  (add-to-list 'load-path "~/git-repositories/org-mode/lisp")
  (add-to-list 'load-path "~/git-repositories/org-mode/contrib/lisp")
  --8<---cut here---end--->8---
  to choose the git version of org-mode. If I run org-reload immediately
  afterwards (which I didn't use to do up to now), the error disappears,
  at least with the minimalist example from my previous post.

Julien.
  




Re: [O] org-agenda time grid broken ?

2017-08-05 Thread Nicolas Goaziou
Hello,

Julien Cubizolles  writes:

> Did I miss an important change to the way org-agenda-files is to be
> used ?

It is probably related to the change in `org-agenda-time-grid'. See new
docstring.


Regards,

-- 
Nicolas Goaziou



[O] org-agenda time grid broken ?

2017-08-05 Thread Julien Cubizolles
I noticed today (I hadn't used it in a long time) that the today and/or
time-grid view in the agenda seems broken.

With emacs -Q running Org mode version 9.0.9 (release_9.0.9 @ 
/usr/share/emacs/26.0.50/lisp/org/)

(setq org-agenda-files '("~/tmp/test-org/todo.org"))

todo.org
--8<---cut here---start->8---
# -*- coding: utf-8 -*-
* Beach
<2017-08-05 sam. 14:00-15:00>
--8<---cut here---end--->8---

org-agenda gives, as expected:
--8<---cut here---start->8---
Week-agenda (W31):
Monday 31 July 2017 W31
Tuesday 1 August 2017
Wednesday   2 August 2017
Thursday3 August 2017
Friday  4 August 2017
Saturday5 August 2017
   8:00.. 
  10:00.. 
  12:00.. 
  todo:   14:00-15:00 Beach
  14:00.. 
  16:00.. 
  18:00.. 
  20:00.. 
  23:17.. now - - - - - - - - - - - - - - - - - - - - - - - - -
Sunday  6 August 2017
--8<---cut here---end--->8---

However, with Org mode version 9.0.9 (release_9.0.9 @ 
/home/wilk/git-repositories/org-mode/lisp/)

the info for today are missing: org-agenda gives (notice Saturday is missing)

--8<---cut here---start->8---
Week-agenda (W31):
Monday 31 July 2017 W31
Tuesday 1 August 2017
Wednesday   2 August 2017
Thursday3 August 2017
Friday  4 August 2017
--8<---cut here---end--->8---

and attempting to switch to the day view gives the following message

--8<---cut here---start->8---
org-agenda-check-type: No Org agenda currently displayed
--8<---cut here---end--->8---

Did I miss an important change to the way org-agenda-files is to be
used ?

Julien.




Re: [O] org-agenda-highlight-todo may erroneously pickup icon 'display property.

2017-05-30 Thread Nicolas Goaziou
Hello,

Keith David Bershatsky  writes:

> Depending upon a user's `org-agenda-prefix-format` (e.g., "%i %-10:c%
> t%s"), `org-agenda-highlight-todo` may erroneously pickup an icon
> `'display` property and then include/duplicate that icon in a new
> space between the todo-keyword and the priority. I chose tho fix this
> in my own setup with `org-plist-delete` to remove the `'display` pair
> of PROPERTY / VALUE from the plist of text properties that are copied
> to the new space " " that is concatenated between the todo-keyword and
> the priority.

I only received this message yesterday, for some reason, hence the
delay.

Would you mind proving a patch for that, using "git format-patch" and an
appropriate commit message?

Thank you.

Regards,

-- 
Nicolas Goaziou



[O] org-agenda-highlight-todo may erroneously pickup icon 'display property.

2017-01-19 Thread Keith David Bershatsky
Depending upon a user's `org-agenda-prefix-format` (e.g., "%i %-10:c% t%s"), 
`org-agenda-highlight-todo` may erroneously pickup an icon `'display` property 
and then include/duplicate that icon in a new space between the todo-keyword 
and the priority.  I chose tho fix this in my own setup with `org-plist-delete` 
to remove the `'display` pair of PROPERTY / VALUE from the plist of text 
properties that are copied to the new space " " that is concatenated between 
the todo-keyword and the priority.

Thanks,

Keith



Re: [O] org-agenda timetable

2017-01-17 Thread Emilio J . Padrón González
Hi!

On Fri, Jan 13, 2017 at 03:45:27PM +, Eric S Fraga wrote:
> >>
> >> I'm using org-agenda [...] I'd like to get the information from the
> >> org-agenda and display it as a "timetable".
> >
> > Did you get a satisfactory solution?
> 
> Not sure what is wanted here but maybe calfw is what you want?

Hei, that's pretty cool!

I'm giving it a try right now and calfw-org is just what I was looking
for :-)

Thanks a lot!

Cheers,
E



Re: [O] org-agenda timetable

2017-01-15 Thread Emilio J . Padrón González
Hi!

Sorry for taking this message from the past, but I'm looking for the
same thing:

On Fri, Nov 13, 2015 at 05:49:06PM -0500, xD wrote:
> 
> I'm using org-agenda [...] I'd like to get the information from the
> org-agenda and display it as a "timetable".

Did you get a satisfactory solution?

Thanks in advance!

Cheers,
E



Re: [O] org-agenda timetable

2017-01-13 Thread Eric S Fraga
On Friday, 13 Jan 2017 at 11:21, Emilio J. Padrón González wrote:
> Hi everyone!
>
> Sorry for taking back this message from the past, but I'm looking for
> the same thing:
>
> On Fri, Nov 13, 2015 at 05:49:06PM -0500, xD wrote:
>>
>> I'm using org-agenda [...] I'd like to get the information from the
>> org-agenda and display it as a "timetable".
>
> Did you get a satisfactory solution?

Not sure what is wanted here but maybe calfw is what you want?

https://github.com/kiwanami/emacs-calfw

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-201-ga51c6f


signature.asc
Description: PGP signature


Re: [O] org-agenda timetable

2017-01-13 Thread Emilio J . Padrón González
Hi everyone!

Sorry for taking back this message from the past, but I'm looking for
the same thing:

On Fri, Nov 13, 2015 at 05:49:06PM -0500, xD wrote:
>
> I'm using org-agenda [...] I'd like to get the information from the
> org-agenda and display it as a "timetable".

Did you get a satisfactory solution?

Thanks in advance!

Cheers,
E



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-05 Thread Nicolas Goaziou
Hello,

yanmcbe  writes:

> Wow, this issue comes very close to something I struggled for hours with
> (3h42') last year.
>
> It finally boiled down to this: sorting by effort in the agenda view only
> works (correctly) when org-agenda-remove-tags is t. Here's the (edited) ECM
> I created for IRC and eventually the list: http://paste.lisp.org/+7723
>
> Is that still expected behaviour? Lack of documentation? The updated
> org-agenda-compare-effort Nicolas provided doesn't solve this, at
> least.

I think this issue was fixed a couple of months ago. At least, I cannot
reproduce it in Org 9.0.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread yanmcbe
Wow, this issue comes very close to something I struggled for hours with
(3h42') last year.

It finally boiled down to this: sorting by effort in the agenda view only
works (correctly) when org-agenda-remove-tags is t. Here's the (edited) ECM
I created for IRC and eventually the list: http://paste.lisp.org/+7723

Is that still expected behaviour? Lack of documentation? The updated
org-agenda-compare-effort Nicolas provided doesn't solve this, at least.

Thanks
Yan

On Wed, Jan 4, 2017 at 10:10 PM, wtm  wrote:

> After some additional testing, I was able to isolate the problem:
> org-agenda-filter-by-effort only filtered entries that had no tags or
> tag inheritance.  This leads me to believe that I just don't
> understand how this command, org-agenda-filter-by-effort, is actually
> supposed to work.  If I have an entry like this:
>
> * TODO task 1  :tag:
> :PROPERTIES:
> :Effort: 0:30
> :END:
>
> And one like this:
>
> * TODO task 2
> :PROPERTIES:
> :Effort: 0:30
> :END:
>
> And I've added the org file to the agenda list and created the
> appropriate org-global-properties:
>
> (setq org-global-properties
>   '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00")))
>
> Shouldn't org-agenda-filter-by-effort set to = "0:30" show both of
> those tasks?  In my case, I'm only seeing this one:
>
> * TODO task 2
> :PROPERTIES:
> :Effort: 0:30
> :END:
>
> On Tue, Jan 3, 2017 at 3:50 PM, wtm  wrote:
> > Thanks, Nicolas.  After adding that code to my config, I tried it
> > again and although the message "invalid face reference" no longer
> > displays, I'm still unable to see any of the entries
> >
> > I also tried it without any custom configuration except the addition
> > of the code you sent.  I had the same result:  no more "invalid face
> > reference" but no display of expected entries after filtering for
> > effort.
> >
> > Perhaps I'm missing something very simple?  If you have any
> > suggestions, I'd love to try them.
> >
> > On Tue, Jan 3, 2017 at 3:29 PM, Nicolas Goaziou 
> wrote:
> >> wtm  writes:
> >>
> >>> I'm installing org-mode from elpa.  Until that update is available
> >>> would using the "org-faces.el" file in the latest git commit
> >>> (http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;
> h=3bba31ff44033e895fedd99857363dd5b0586b41)
> >>> work?
> >>
> >> Meanwhile, you only need to put the following somewhere in your config:
> >>
> >>   (defface org-agenda-filter-effort '((t :inherit mode-line))
> >> "Face for effort in the mode-line when filtering the agenda."
> >> :group 'org-faces)
> >>
> >>
> >> Regards,
>
>


Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread wtm
Works perfectly.  Thank you, Nicolas!

On Wed, Jan 4, 2017 at 4:40 PM, Nicolas Goaziou  wrote:
> wtm  writes:
>
>> Wonderful!  Is there any elisp that I could add to my config to test
>> it?  I would love have this capability.
>
> You need to eval
>
>   (defun org-agenda-compare-effort (op value)
> "Compare the effort of the current line with VALUE, using OP.
>   If the line does not have an effort defined, return nil."
> (let ((effort (get-text-property 0 'effort-minutes (org-get-at-bol 
> 'txt
>   (funcall op
>(or effort (if org-sort-agenda-noeffort-is-high 32767 -1))
>value)))
>
> Regards,



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread Nicolas Goaziou
wtm  writes:

> Wonderful!  Is there any elisp that I could add to my config to test
> it?  I would love have this capability.

You need to eval

  (defun org-agenda-compare-effort (op value)
"Compare the effort of the current line with VALUE, using OP.
  If the line does not have an effort defined, return nil."
(let ((effort (get-text-property 0 'effort-minutes (org-get-at-bol 'txt
  (funcall op
   (or effort (if org-sort-agenda-noeffort-is-high 32767 -1))
   value)))

Regards,



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread wtm
Wonderful!  Is there any elisp that I could add to my config to test
it?  I would love have this capability.

On Wed, Jan 4, 2017 at 4:31 PM, Nicolas Goaziou  wrote:
> Hello,
>
> wtm  writes:
>
>> After some additional testing, I was able to isolate the problem:
>> org-agenda-filter-by-effort only filtered entries that had no tags or
>> tag inheritance.  This leads me to believe that I just don't
>> understand how this command, org-agenda-filter-by-effort, is actually
>> supposed to work.  If I have an entry like this:
>>
>> * TODO task 1  :tag:
>> :PROPERTIES:
>> :Effort: 0:30
>> :END:
>>
>> And one like this:
>>
>> * TODO task 2
>> :PROPERTIES:
>> :Effort: 0:30
>> :END:
>>
>> And I've added the org file to the agenda list and created the
>> appropriate org-global-properties:
>>
>> (setq org-global-properties
>>   '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00")))
>>
>> Shouldn't org-agenda-filter-by-effort set to = "0:30" show both of
>> those tasks?  In my case, I'm only seeing this one:
>>
>> * TODO task 2
>> :PROPERTIES:
>> :Effort: 0:30
>> :END:
>
> Good catch. There was an issue in "org-agenda.el". It is now fixed.
> Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread Nicolas Goaziou
Hello,

wtm  writes:

> After some additional testing, I was able to isolate the problem:
> org-agenda-filter-by-effort only filtered entries that had no tags or
> tag inheritance.  This leads me to believe that I just don't
> understand how this command, org-agenda-filter-by-effort, is actually
> supposed to work.  If I have an entry like this:
>
> * TODO task 1  :tag:
> :PROPERTIES:
> :Effort: 0:30
> :END:
>
> And one like this:
>
> * TODO task 2
> :PROPERTIES:
> :Effort: 0:30
> :END:
>
> And I've added the org file to the agenda list and created the
> appropriate org-global-properties:
>
> (setq org-global-properties
>   '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00")))
>
> Shouldn't org-agenda-filter-by-effort set to = "0:30" show both of
> those tasks?  In my case, I'm only seeing this one:
>
> * TODO task 2
> :PROPERTIES:
> :Effort: 0:30
> :END:

Good catch. There was an issue in "org-agenda.el". It is now fixed.
Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-04 Thread wtm
After some additional testing, I was able to isolate the problem:
org-agenda-filter-by-effort only filtered entries that had no tags or
tag inheritance.  This leads me to believe that I just don't
understand how this command, org-agenda-filter-by-effort, is actually
supposed to work.  If I have an entry like this:

* TODO task 1  :tag:
:PROPERTIES:
:Effort: 0:30
:END:

And one like this:

* TODO task 2
:PROPERTIES:
:Effort: 0:30
:END:

And I've added the org file to the agenda list and created the
appropriate org-global-properties:

(setq org-global-properties
  '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00")))

Shouldn't org-agenda-filter-by-effort set to = "0:30" show both of
those tasks?  In my case, I'm only seeing this one:

* TODO task 2
:PROPERTIES:
:Effort: 0:30
:END:

On Tue, Jan 3, 2017 at 3:50 PM, wtm  wrote:
> Thanks, Nicolas.  After adding that code to my config, I tried it
> again and although the message "invalid face reference" no longer
> displays, I'm still unable to see any of the entries
>
> I also tried it without any custom configuration except the addition
> of the code you sent.  I had the same result:  no more "invalid face
> reference" but no display of expected entries after filtering for
> effort.
>
> Perhaps I'm missing something very simple?  If you have any
> suggestions, I'd love to try them.
>
> On Tue, Jan 3, 2017 at 3:29 PM, Nicolas Goaziou  
> wrote:
>> wtm  writes:
>>
>>> I'm installing org-mode from elpa.  Until that update is available
>>> would using the "org-faces.el" file in the latest git commit
>>> (http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=3bba31ff44033e895fedd99857363dd5b0586b41)
>>> work?
>>
>> Meanwhile, you only need to put the following somewhere in your config:
>>
>>   (defface org-agenda-filter-effort '((t :inherit mode-line))
>> "Face for effort in the mode-line when filtering the agenda."
>> :group 'org-faces)
>>
>>
>> Regards,



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread wtm
Thanks, Nicolas.  After adding that code to my config, I tried it
again and although the message "invalid face reference" no longer
displays, I'm still unable to see any of the entries

I also tried it without any custom configuration except the addition
of the code you sent.  I had the same result:  no more "invalid face
reference" but no display of expected entries after filtering for
effort.

Perhaps I'm missing something very simple?  If you have any
suggestions, I'd love to try them.

On Tue, Jan 3, 2017 at 3:29 PM, Nicolas Goaziou  wrote:
> wtm  writes:
>
>> I'm installing org-mode from elpa.  Until that update is available
>> would using the "org-faces.el" file in the latest git commit
>> (http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=3bba31ff44033e895fedd99857363dd5b0586b41)
>> work?
>
> Meanwhile, you only need to put the following somewhere in your config:
>
>   (defface org-agenda-filter-effort '((t :inherit mode-line))
> "Face for effort in the mode-line when filtering the agenda."
> :group 'org-faces)
>
>
> Regards,



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread Nicolas Goaziou
wtm  writes:

> I'm installing org-mode from elpa.  Until that update is available
> would using the "org-faces.el" file in the latest git commit
> (http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=3bba31ff44033e895fedd99857363dd5b0586b41)
> work?

Meanwhile, you only need to put the following somewhere in your config:

  (defface org-agenda-filter-effort '((t :inherit mode-line))
"Face for effort in the mode-line when filtering the agenda."
:group 'org-faces)


Regards,



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread wtm
Nicolas,

Thank you for finding that problem so quickly!  It's vexed me for some time.

I'm installing org-mode from elpa.  Until that update is available
would using the "org-faces.el" file in the latest git commit
(http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=3bba31ff44033e895fedd99857363dd5b0586b41)
work?

Will

On Tue, Jan 3, 2017 at 3:15 PM, Nicolas Goaziou  wrote:
> Hello,
>
> Jorge Morais Neto  writes:
>
>> On 3 January 2017 at 14:16, Nicolas Goaziou  wrote:
>>> I cannot reproduce it with, e.g.
>>>
>>>   * TODO test
>>>   :PROPERTIES:
>>>   :Effort:   2:00
>>>   :END:
>>>
>>> and a bare configuration. Could you double-check you're really using Org
>>> 9.0.3?
>> I reproduce it (the behavior and the message in *Messages*) with my own
>> files and configuration.  I have not tested with a bare configuration.  I 
>> have
>> tested org-agenda-filter-by-effort with both operator = and operator <.
>
> I can reproduce it now.
>
> Fixed. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread Nicolas Goaziou
Hello,

Jorge Morais Neto  writes:

> On 3 January 2017 at 14:16, Nicolas Goaziou  wrote:
>> I cannot reproduce it with, e.g.
>>
>>   * TODO test
>>   :PROPERTIES:
>>   :Effort:   2:00
>>   :END:
>>
>> and a bare configuration. Could you double-check you're really using Org
>> 9.0.3?
> I reproduce it (the behavior and the message in *Messages*) with my own
> files and configuration.  I have not tested with a bare configuration.  I have
> tested org-agenda-filter-by-effort with both operator = and operator <.

I can reproduce it now.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread Jorge Morais Neto
On 3 January 2017 at 14:16, Nicolas Goaziou  wrote:
> I cannot reproduce it with, e.g.
>
>   * TODO test
>   :PROPERTIES:
>   :Effort:   2:00
>   :END:
>
> and a bare configuration. Could you double-check you're really using Org
> 9.0.3?
I reproduce it (the behavior and the message in *Messages*) with my own
files and configuration.  I have not tested with a bare configuration.  I have
tested org-agenda-filter-by-effort with both operator = and operator <.

org-version reports
  Org mode version 9.0.3 (9.0.3-elpaplus @
/home/jorge/.emacs.d/elpa/org-plus-contrib-20161224/)

emacs-version reports
  GNU Emacs 25.1.91.1 (x86_64-unknown-linux-gnu, GTK+ Version
3.18.9) of 2016-12-31

Regards
-- 
• I am Brazilian.  I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread wtm
Nicolas,

Thanks for responding.  Here's what I get when I enter M-x org-version:

Org mode version 9.0.3 (9.0.3-elpa @ c:/Users/Will/.emacs.d/elpa/org-20161224/)

Will

On Tue, Jan 3, 2017 at 11:16 AM, Nicolas Goaziou  wrote:
> Hello,
>
> wtm  writes:
>
>> I'm having trouble using org-agenda-filter-by-effort on existing
>> agendas in orgmode 9.0.3 in GNU Emacs 25.1.1 ([x86_64-w64-mingw32] of
>> 2016-09-17).  Each time I attempt to use org-agenda-filter-by-effort,
>> I type "_" and then "=" and I select the one-digit index of the effort
>> estimate I want--in my case, I select "3" which corresponds to "0:30".
>>
>> Instead of seeing only those orgmode TODO headings that have an effort
>> property of "0:30" in the agenda buffer as I would expect, all the
>> TODO headings disappear.  However, every other type of filter on the
>> agenda buffer seems to work.  I can easily filter by category and tag.
>> I have attempted this with my configuration and without any custom
>> configuration at all and always gotten the same result.
>>
>> Although no errors occur (at least none that M-x toggle-debug-on-error
>> pick up) the *Messages* buffer provides some feedback: "Invalid face
>> reference: org-agenda-filter-effort [2 times]".
>
> [...]
>
>> I've attempted to reproduce the problem in Emacs 25.1.1 and orgmode
>> 9.0.3 without any configuration and still experienced the same
>> problem.  To reproduce the problem I think you'd only need to create
>> an org file, add an entry with a TODO heading, and then assign an
>> effort estimate that corresponds to the array of allowed values (see
>> description of org-agenda-filter-by-effort http://bit.ly/2iF4o68).
>> After that, you'd need to create an agenda by entering "C-c a"
>> (org-agenda) and "t" (List all TODO entries).
>
> I cannot reproduce it with, e.g.
>
>   * TODO test
>   :PROPERTIES:
>   :Effort:   2:00
>   :END:
>
> and a bare configuration. Could you double-check you're really using Org
> 9.0.3?
>
> Regards,
>
> --
> Nicolas Goaziou



Re: [O] org-agenda-filter-effort and "invalid face reference"

2017-01-03 Thread Nicolas Goaziou
Hello,

wtm  writes:

> I'm having trouble using org-agenda-filter-by-effort on existing
> agendas in orgmode 9.0.3 in GNU Emacs 25.1.1 ([x86_64-w64-mingw32] of
> 2016-09-17).  Each time I attempt to use org-agenda-filter-by-effort,
> I type "_" and then "=" and I select the one-digit index of the effort
> estimate I want--in my case, I select "3" which corresponds to "0:30".
>
> Instead of seeing only those orgmode TODO headings that have an effort
> property of "0:30" in the agenda buffer as I would expect, all the
> TODO headings disappear.  However, every other type of filter on the
> agenda buffer seems to work.  I can easily filter by category and tag.
> I have attempted this with my configuration and without any custom
> configuration at all and always gotten the same result.
>
> Although no errors occur (at least none that M-x toggle-debug-on-error
> pick up) the *Messages* buffer provides some feedback: "Invalid face
> reference: org-agenda-filter-effort [2 times]".

[...]

> I've attempted to reproduce the problem in Emacs 25.1.1 and orgmode
> 9.0.3 without any configuration and still experienced the same
> problem.  To reproduce the problem I think you'd only need to create
> an org file, add an entry with a TODO heading, and then assign an
> effort estimate that corresponds to the array of allowed values (see
> description of org-agenda-filter-by-effort http://bit.ly/2iF4o68).
> After that, you'd need to create an agenda by entering "C-c a"
> (org-agenda) and "t" (List all TODO entries).

I cannot reproduce it with, e.g.

  * TODO test
  :PROPERTIES:
  :Effort:   2:00
  :END:

and a bare configuration. Could you double-check you're really using Org
9.0.3?

Regards,

-- 
Nicolas Goaziou



[O] org-agenda-filter-effort and "invalid face reference"

2017-01-01 Thread wtm
Hello,

I'm having trouble using org-agenda-filter-by-effort on existing
agendas in orgmode 9.0.3 in GNU Emacs 25.1.1 ([x86_64-w64-mingw32] of
2016-09-17).  Each time I attempt to use org-agenda-filter-by-effort,
I type "_" and then "=" and I select the one-digit index of the effort
estimate I want--in my case, I select "3" which corresponds to "0:30".

Instead of seeing only those orgmode TODO headings that have an effort
property of "0:30" in the agenda buffer as I would expect, all the
TODO headings disappear.  However, every other type of filter on the
agenda buffer seems to work.  I can easily filter by category and tag.
I have attempted this with my configuration and without any custom
configuration at all and always gotten the same result.

Although no errors occur (at least none that M-x toggle-debug-on-error
pick up) the *Messages* buffer provides some feedback: "Invalid face
reference: org-agenda-filter-effort [2 times]".

I've tried searching for information about the "invalid face
reference" message and orgmode.  I've found a few discussions on the
orgmode listserv, one of them that occurred recently (November 4,
2016).  However, the version of orgmode in this most recent discussion
is 8.3 and I'm using orgmode 9.0.3.  And it appears that the patch
described has already been applied.  I also inspected org-agenda.el
for the changes and they appear to be there (although I'm not a very
experienced elisp programmer or debugger).

[O] [PATCH] org-agenda.el Correct :inherit on org-agenda-fontify-priorit
https://lists.gnu.org/archive/html/emacs-orgmode/2016-11/msg00057.html

[O] `invalid face reference nil` caused by `org-agenda-fontify-propertie
https://lists.gnu.org/archive/html/emacs-orgmode/2015-05/msg00116.html

[O] Bug: Priority #B in Agenda causes invalid face reference [8.2.1 (8.2
https://lists.gnu.org/archive/html/emacs-orgmode/2013-10/msg00870.html

I've attempted to reproduce the problem in Emacs 25.1.1 and orgmode
9.0.3 without any configuration and still experienced the same
problem.  To reproduce the problem I think you'd only need to create
an org file, add an entry with a TODO heading, and then assign an
effort estimate that corresponds to the array of allowed values (see
description of org-agenda-filter-by-effort http://bit.ly/2iF4o68).
After that, you'd need to create an agenda by entering "C-c a"
(org-agenda) and "t" (List all TODO entries).

I'm at a loss as to what steps to attempt next to troubleshoot this.
I've seen an intriguing discussion on Stack Exchange about "font lock
studio" but I couldn't get it to work.  I'd appreciate any tips you
might have on how to proceed.

Thanks and Happy New Year to all my fellow org-mode users!

Will



Re: [O] org-agenda fails on particular construct

2016-12-15 Thread Nicolas Goaziou
Hello,

Ingo Lohmar  writes:

> The culprit seems to be in org-agenda.el, ll. 6098 ff., in 
> org-agenda-get-deadlines:
>
>  ((eq org-agenda-skip-deadline-prewarning-if-scheduled
>   'pre-scheduled)
>   ;; Set pre-warning to no earlier than SCHEDULED.
>   (min (- deadline scheduled) org-deadline-warning-days))
>
> So it needs an item with deadline *and* scheduled time, and the
> 'pre-scheduled setting of the config var
> org-agenda-skip-deadline-prewarning-if-scheduled.
>
> Subtracting "scheduled" fails: every date in the procedure is an
> integer, scheduled is still the raw string from the item.  At the
> moment, I am too tired to figure out why that is, sorry.  Hope this is
> still of some help.

Good catch. Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda fails on particular construct

2016-12-15 Thread Ingo Lohmar
On Thu, Dec 15 2016 21:02 (+0100), Ingo Lohmar wrote:

> [Sorry for not replying in-thread...]
>
> Hi All,
>
> after updating I'm getting the same result, but I could not reproduce it
> even with my org-config until now.
>
> The culprit seems to be in org-agenda.el, ll. 6098 ff., in 
> org-agenda-get-deadlines:
>
>  ((eq org-agenda-skip-deadline-prewarning-if-scheduled
>   'pre-scheduled)
>   ;; Set pre-warning to no earlier than SCHEDULED.
>   (min (- deadline scheduled) org-deadline-warning-days))
>
> So it needs an item with deadline *and* scheduled time, and the
> 'pre-scheduled setting of the config var
> org-agenda-skip-deadline-prewarning-if-scheduled.
>
> Subtracting "scheduled" fails: every date in the procedure is an
> integer, scheduled is still the raw string from the item.  At the
> moment, I am too tired to figure out why that is, sorry.  Hope this is
> still of some help.

It seems replacing "scheduled" by (org-agenda--timestamp-to-absolute
scheduled) does the trick, but I have zero idea about the other args
that can be passed (down to org-time-string-to-absolute).



Re: [O] org-agenda fails on particular construct

2016-12-15 Thread Ingo Lohmar
[Sorry for not replying in-thread...]

Hi All,

after updating I'm getting the same result, but I could not reproduce it
even with my org-config until now.

The culprit seems to be in org-agenda.el, ll. 6098 ff., in 
org-agenda-get-deadlines:

   ((eq org-agenda-skip-deadline-prewarning-if-scheduled
'pre-scheduled)
;; Set pre-warning to no earlier than SCHEDULED.
(min (- deadline scheduled) org-deadline-warning-days))

So it needs an item with deadline *and* scheduled time, and the
'pre-scheduled setting of the config var
org-agenda-skip-deadline-prewarning-if-scheduled.

Subtracting "scheduled" fails: every date in the procedure is an
integer, scheduled is still the raw string from the item.  At the
moment, I am too tired to figure out why that is, sorry.  Hope this is
still of some help.



Re: [O] org-agenda fails on particular construct

2016-12-15 Thread Nicolas Goaziou
Hello,

Jeffrey DeLeo  writes:

> With latest version of org:
>
> Org mode version 9.0.2 (9.0.2-elpaplus @
> /home/me/.emacs.d/elpa/org-plus-contrib-20161214/)
>
> I get the following error when trying to create an agenda:
>
> org-agenda-get-day-entries:
> Wrong type argument: number-or-marker-p, "<2015-03-07 Sat>"
>
> with a construct like this:
>
> *** DONE Do Something
> CLOSED: [2015-03-05 Thu 15:14] SCHEDULED: <2015-03-05 Thu> DEADLINE: 
> <2015-03-07 Sat>

I cannot reproduce it. Could you provide an ECM and a more complete
backtrace?

Regards,
-- 
Nicolas Goaziou



[O] org-agenda fails on particular construct

2016-12-14 Thread Jeffrey DeLeo
With latest version of org:

Org mode version 9.0.2 (9.0.2-elpaplus @
/home/me/.emacs.d/elpa/org-plus-contrib-20161214/)

I get the following error when trying to create an agenda:

org-agenda-get-day-entries:
Wrong type argument: number-or-marker-p, "<2015-03-07 Sat>"

with a construct like this:

*** DONE Do Something
CLOSED: [2015-03-05 Thu 15:14] SCHEDULED: <2015-03-05 Thu> DEADLINE: 
<2015-03-07 Sat>

When SCHEDULED and DEADLINE removed, no problem.





Re: [O] org-agenda-list: no-catch --cl-block-nil--

2016-11-25 Thread Karl Voit
* Nicolas Goaziou  wrote:
> Hello,
>
> Karl Voit  writes:
>
>> I get an error when calling org-agenda-list after updating my
>> main-branch of Org-mode:
>>
>> GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
>> Org mode version 9.0.1 (release_9.0.1-12-g2e35a5)
>>
>> Debug output:
>>
>>   throw(--cl-block-nil-- (quote (space :width (16
>
> It looks like a bug in Emacs 24.5. I pushed a tentative fix. Could you
> update Org (maint) and try again?

Aaaand it is fixed.

Unbelievable fast fix. :-O

Thanks for your work!

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github




Re: [O] org-agenda-list: no-catch --cl-block-nil--

2016-11-25 Thread Nicolas Goaziou
Hello,

Karl Voit  writes:

> I get an error when calling org-agenda-list after updating my
> main-branch of Org-mode:
>
> GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
> Org mode version 9.0.1 (release_9.0.1-12-g2e35a5)
>
> Debug output:
>
>   throw(--cl-block-nil-- (quote (space :width (16

It looks like a bug in Emacs 24.5. I pushed a tentative fix. Could you
update Org (maint) and try again?

Regards,

-- 
Nicolas Goaziou



[O] org-agenda-list: no-catch --cl-block-nil--

2016-11-25 Thread Karl Voit
Hi!

I get an error when calling org-agenda-list after updating my
main-branch of Org-mode:

GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
Org mode version 9.0.1 (release_9.0.1-12-g2e35a5)

Debug output:

  throw(--cl-block-nil-- (quote (space :width (16
  org-agenda-get-category-icon("refinement")
  org-agenda-format-item("Sched. 2x: " #("NEXT get confidence-level green on 
[[IPD:13673]] :refinement:" 0 4 (face 
(:foreground "red" :weight bold) fontified nil org-category "refinement") 4 35 
(face org-level-3 fontified nil org-category "refinement") 35 36 (face org-link 
invisible org-link keymap (keymap (follow-link . mouse-face) (mouse-3 . 
org-find-file-at-mouse) (mouse-2 . org-open-at-mouse)) mouse-face highlight 
font-lock-multiline t help-echo "LINK: 
http://product.mycompany.at/jira/browse/IPD-13673; htmlize-link (:uri 
"http://product.mycompany.at/jira/browse/IPD-13673;) fontified nil org-category 
"refinement") 36 37 (face org-link invisible org-link keymap (keymap 
(follow-link . mouse-face) (mouse-3 . org-find-file-at-mouse) (mouse-2 . 
org-open-at-mouse)) mouse-face highlight font-lock-multiline t help-echo "LINK: 
http://product.mycompany.at/jira/browse/IPD-13673; htmlize-link (:uri 
"http://product.mycompany.at/jira/browse/IPD-13673;) re
 ar-nonsticky (mouse-face highlight keymap invisible intangible help-echo 
org-linked-text htmlize-link) fontified nil org-category "refinement") 37 45 
(face org-link keymap (keymap (follow-link . mouse-face) (mouse-3 . 
org-find-file-at-mouse) (mouse-2 . org-open-at-mouse)) mouse-face highlight 
font-lock-multiline t help-echo "LINK: 
http://product.mycompany.at/jira/browse/IPD-13673; htmlize-link (:uri 
"http://product.mycompany.at/jira/browse/IPD-13673;) fontified nil org-category 
"refinement") 45 46 (face org-link keymap (keymap (follow-link . mouse-face) 
(mouse-3 . org-find-file-at-mouse) (mouse-2 . org-open-at-mouse)) mouse-face 
highlight font-lock-multiline t help-echo "LINK: 
http://product.mycompany.at/jira/browse/IPD-13673; htmlize-link (:uri 
"http://product.mycompany.at/jira/browse/IPD-13673;) rear-nonsticky (mouse-face 
highlight keymap invisible intangible help-echo org-linked-text htmlize-link) 
fontified nil org-category "refinement") 46 47 (face org-link invisible 
org-link ke
 ymap (keymap (follow-link . mouse-face) (mouse-3 . org-find-file-at-mouse) 
(mouse-2 . org-open-at-mouse)) mouse-face highlight font-lock-multiline t 
help-echo "LINK: http://product.mycompany.at/jira/browse/IPD-13673; 
htmlize-link (:uri "http://product.mycompany.at/jira/browse/IPD-13673;) 
fontified nil org-category "refinement") 47 48 (face org-link invisible 
org-link keymap (keymap (follow-link . mouse-face) (mouse-3 . 
org-find-file-at-mouse) (mouse-2 . org-open-at-mouse)) mouse-face highlight 
font-lock-multiline t help-echo "LINK: 
http://product.mycompany.at/jira/browse/IPD-13673; htmlize-link (:uri 
"http://product.mycompany.at/jira/browse/IPD-13673;) rear-nonsticky (mouse-face 
highlight keymap invisible intangible help-echo org-linked-text htmlize-link) 
fontified nil org-category "refinement") 48 89 (face org-level-3 fontified nil 
org-category "refinement") 89 100 (face (org-tag org-level-3) mouse-face 
highlight keymap (keymap (follow-link . mouse-face) (mouse-3 . org-find-file-at
 -mouse) (mouse-2 . org-open-at-mouse)) fontified nil org-category 
"refinement") 100 101 (face (org-tag org-level-3) mouse-face highlight keymap 
(keymap (follow-link . mouse-face) (mouse-3 . org-find-file-at-mouse) (mouse-2 
. org-open-at-mouse)) rear-nonsticky (mouse-face highlight keymap invisible 
intangible help-echo org-linked-text htmlize-link) fontified nil org-category 
"refinement")) "   " "refinement" (#("OrderQuantities" 0 15 (inherited t)) 
#("US_ConfigureOffer" 0 17 (inherited t)) "refinement") time nil nil)
  byte-code("\306 \307\216\310 *\204

I do not have any configuration related to the category
"refinement". I use some icons for categories on my agenda:

(add-to-list 'org-agenda-category-icon-alist
 '(".*" '(space . (:width (16
 )
(add-to-list 'org-agenda-category-icon-alist
 '("contacts" "/usr/share/icons/oxygen/16x16/places/user-identity.png" nil 
nil :ascent center)
 ;;/usr/share/icons/gnome/16x16/emotes/face-smile.png
  )
(add-to-list 'org-agenda-category-icon-alist
 '("public_voit" 
"/usr/share/icons/oxygen/16x16/mimetypes/application-rss+xml.png" nil nil 
:ascent center)
  )
(add-to-list 'org-agenda-category-icon-alist
 '("misc" "/usr/share/icons/oxygen/16x16/emblems/emblem-new.png" nil nil 
:ascent center)
  )
(add-to-list 'org-agenda-category-icon-alist
 '("hardware" "/usr/share/icons/oxygen/16x16/devices/camera-photo.png" nil 
nil :ascent center)
  )
(add-to-list 'org-agenda-category-icon-alist
 '("bwg" "/usr/share/icons/oxygen/16x16/actions/go-home.png" nil nil 
:ascent center)
  )

The content of org-agenda-category-icon-alist 

Re: [O] Org Agenda and recurring icalendar events

2016-09-30 Thread Eric S Fraga
On Friday, 30 Sep 2016 at 08:54, cschr wrote:
> Hello together
>
> Im now running Emacs 25.1 with Org 8.3.5 on Windows.  I love Emacs and
> Orgmode and I want to use it instead of Microsoft Office.  But in
> order to replace MS-Outlook calendar by Org Agenda, and in order to
> sync Org Agenda with my Android phone, I would need all icalendar
> functionality, which is used by MS-Outlook and by Android, implemented
> in Orgmode. Most urgently missing are recurrence features like RRULE,
> EXDATE, DTSTART, DTEND, etc, and import and export of those from and
> to icalendar.  The current implementation is only rudimentary.

Rudimentary but works, at least for me, albeit using Google calendar and
not Outlook as the latter is so non-standard that it's a
nightmare.  Google is marginally better although not fantastic either.

With Google calendar, the easiest way to have org and Android/Windows
synchronised is to use MobileOrg and have it take care of the
synchronisation with the calendar.  This will handle many but not all of
your cases, specifically excluded dates and end dates for recurring
events which org does not support out of the box.

Alternatively, you can have two separate processes for synchronisation
in each direction: converting from ics to org and vice versa.  This has
been discussed many times on the list and there is material on worg.

> I had sent the below emails via bug-gnu-emacs, but there was no
> response – was it the wrong place to send to ?

Not sure whether wrong or not but this mailing list is the best place
for discussions of this form as you are requesting a feature as opposed
to reporting a bug.


-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.1.1, Org release_8.3.6-1131-gd68497



[O] Org Agenda and recurring icalendar events

2016-09-30 Thread cschr
Hello together

 

Im now running Emacs 25.1 with Org 8.3.5 on Windows.   I love Emacs and
Orgmode and I want to use it instead of Microsoft Office.   But in order to
replace MS-Outlook calendar by Org Agenda, and in order to sync Org Agenda
with my Android phone, I would need all icalendar functionality, which is
used by MS-Outlook and by Android, implemented in Orgmode. Most urgently
missing are recurrence features like RRULE, EXDATE, DTSTART, DTEND, etc, and
import and export of those from and to icalendar.   The current
implementation is only rudimentary.

 

Emacs diary is not suitable - import and export from and to icalendar are
also not working properly for most recurring events, and of course it misses
the Orgmode features.

 

My idea would be to introduce recurring icalendar elements like RRULE,
EXDATE, DTSTART and DTEND as Org Properties, which would make importing and
exporting them straightforward, I guess. Main work would be to make these
dates show up in the Org Agenda properly.

 

Wonderful would be to have this functionality as an official part of orgmode
and maintained

 

A similar work was started in 2013 already:
http://thread.gmane.org/gmane.emacs.orgmode/74391

 

But that’s all I was able to find on the web about this subject – it seems
no work is going on here - or does anybody know there is?

 

Im wondering if this idea is of interest to anybody else – to me this is a
real killer feature for using Org Agenda.

 

I had sent the below emails via bug-gnu-emacs, but there was no response –
was it the wrong place to send to ?

 

I don’t have Emacs development knowledge.  Is there any expert here who
could tell me if this is possible at all, whether this could become part of
official orgmode and how, and what could the effort be – is this a few
weeks, or a few months, or much more work ?

 

Thank you so much

 

Kind regards

Chris

 

 

 

 

From: cschr [mailto:cs...@freenet.de] 
Sent: 12 August 2016 09:34
To: bug-gnu-em...@gnu.org
Subject: RE: Subject: 25.0.94; Proposal to make orgmode agenda really useful

 

RRULE might better be an orgmode PROPERTY too, like proposed for Recurrence
End Date and Exceptions in

http://thread.gmane.org/gmane.emacs.orgmode/74391

 

In fact, its several properties, but not all are needed for Android Sync. I
only need: RRULE_FREQ, RRULE_INTERVAL, RRULE_BYDAY, RRULE_COUNT,
RRULE_UNTIL. 

Also, EXDATE is needed which is not part of RRULE but part of VEVENT, and
TRIGGER which is part of VALARM

 

 

From: cschr [  mailto:cs...@freenet.de] 
Sent: 10 August 2016 20:27
To:   bug-gnu-em...@gnu.org
Subject: Subject: 25.0.94; Proposal to make orgmode agenda really useful

 

I love emacs - its incredibly powerful and helpful - its almost all i

ever dreamt of. 

 

One thing i miss urgently: make org agenda files fully sync with my

icalendar files, including recurrance with end dates, and including alarms.

RRule Exceptions would also be helpfull. 

 

Here are my ideas, and I would be curious to hear your plans:

 

1. Would it be an idea to implement a DIARY_RRULE function which can be used

in date sexpr in org agenda (and maybe also the diary) and which accepts

an icalendar RRULE string as parameter ?   This could make icalendar

export and import very easy (just copy the string), and implementation

in elisp shouldnt be too hard (but thats something I can only guess -

you know it better).

 

2. exceptions and end dates could also be implemented as org properties,

as already proposed by  
http://thread.gmane.org/gmane.emacs.orgmode/74391

 

3. At the moment i am stuck because my icalendar file can only be

imported into the diary: import into org files is restricted to single
events

(and maybe very simple recurring events?). And the diary import uses
diary-date

a lot which cannot be exported, and diary export does not create VALARms,

and the ORG features are not available for the diary.

 

Thanks a lot for your great work !!!

Kind regards – Christoph Schröder, Cham, Switzerland

 

 



Re: [O] org-agenda: different face (color) per file?

2016-09-16 Thread Adam Porter
Understandable.  :)  Well, another option would be to create a custom
agenda command that put items from different files in different
sections.  Check the docs for the org-agenda-custom-commands variable
(and google it for many examples).




Re: [O] org-agenda: different face (color) per file?

2016-09-16 Thread Xebar Saram
hehe thx

both are way over my head :)

ill just give up on the idea ;-)

thx!

Z

On Fri, Sep 16, 2016 at 9:34 AM, Adam Porter  wrote:

> Xebar Saram  writes:
>
> > this seems it should be trivial but googling didnt help. my org-agenda
> > view is made out of 5-6 files. can one define a different face (mainly
> > color) per file?
>
> There's no way to do this that I know of, but I guess you could try two
> approaches:
>
> 1.  Advise the code that writes the agenda line-by-line.  You'll have to
> dig through the agenda-making code...
>
> 2.  Write a function to post-process the agenda and adjust the color of
> each line depending on its source file (or its category, which is
> usually the file it comes from).  I'm guessing this would be easier.
>
>
>


Re: [O] org-agenda: different face (color) per file?

2016-09-16 Thread Adam Porter
Xebar Saram  writes:

> this seems it should be trivial but googling didnt help. my org-agenda
> view is made out of 5-6 files. can one define a different face (mainly
> color) per file?

There's no way to do this that I know of, but I guess you could try two
approaches:

1.  Advise the code that writes the agenda line-by-line.  You'll have to
dig through the agenda-making code...

2.  Write a function to post-process the agenda and adjust the color of
each line depending on its source file (or its category, which is
usually the file it comes from).  I'm guessing this would be easier.




[O] org-agenda: different face (color) per file?

2016-09-15 Thread Xebar Saram
Hi all,

this seems it should be trivial but googling didnt help. my org-agenda view
is made out of 5-6 files. can one define a different face (mainly color)
per file?

thx!

Z


Re: [O] Org-agenda-sorting: can I sort by inactive timestamps?

2016-05-30 Thread Matt Lundin
"Martin Beck"  writes:

> I'm using inactive timestamps to show the creation date of a new
> heading and also to show the modification dates with some short text
> notes about the progress in there:
>  
> Example:
>  
> * Headings Test
> <2016-05-30 Mo 13:18>
> * Heading 1
> [2016-05-30 Mo 13:21]
> * Heading 2
> [2016-05-30 Mo 13:16]
> * Heading 3
> [2016-05-30 Mo 13:16]
> * TODO Find out about sorting by timestamp
> [2016-05-30 Mo 13:12]
> [2016-05-30 Mo 14:22]
> posted question to org-mode users group
>  
>  
> I tried the timestamp-up/timestamp-down sorting criteria in my agenda,
> but they seem to ignore the inactive timestamps:
> ("r" "Refile" tags "+refile+LEVEL=1"
>   ((org-agenda-overriding-header "Refile")
>(org-agenda-sorting-strategy
> (quote
>  (timestamp-up)

> I also tried to use the table-view of the agenda, but in the column
> "timestamp" it only shows the active timestamp of the first heading.
> Questions:
> - is it possible to use inactive timestamps for sorting the agenda?

The timestamp-up here retrieves active timestamps. For inactive
timestamps, you can use tsia-up. See the docstring (C-h v) for
org-agenda-sorting-strategy:

tsia-upSort by inactive timestamp, early first
tsia-down  Sort by inactive timestamp, late first

> - what happens if I have several timestamps (active or inactive) in
> one heading? Will org-mode take the first/last one in the plain text
> "code" or the newest or oldest one by date?

With tsia-up or tsia-down, org will use the first inactive timestamp in
the heading. 

For more details, see...

http://orgmode.org/manual/Special-properties.html

Matt




[O] Org-agenda-sorting: can I sort by inactive timestamps?

2016-05-30 Thread Martin Beck
I'm using inactive timestamps to show the creation date of a new heading and also to show the modification dates with some short text notes about the progress in there:

 

Example:


 

* Headings Test
<2016-05-30 Mo 13:18>
* Heading 1

[2016-05-30 Mo 13:21]
* Heading 2
[2016-05-30 Mo 13:16]
* Heading 3
[2016-05-30 Mo 13:16]
* TODO Find out about sorting by timestamp

[2016-05-30 Mo 13:12]

[2016-05-30 Mo 14:22]

posted question to org-mode users group

 

 

I tried the timestamp-up/timestamp-down sorting criteria in my agenda, but they seem to ignore the inactive timestamps:

("r" "Refile" tags "+refile+LEVEL=1"
  ((org-agenda-overriding-header "Refile")
   (org-agenda-sorting-strategy
    (quote
     (timestamp-up)

 

I also tried to use the table-view of the agenda, but in the column "timestamp" it only shows the active timestamp of the first heading.

 

Questions:

- is it possible to use inactive timestamps for sorting the agenda?

- what happens if I have several timestamps (active or inactive) in one heading? Will org-mode take the first/last one in the plain text "code" or the newest or oldest one by date?

Both could make sense to me, so it would be interesting to have both possibilities..

 

Kind regards

 

Martin




Re: [O] org agenda persistent mark

2016-05-26 Thread Nicolas Goaziou
Hello,

Jesse Johnson  writes:

> When I enable persistent marks while performing bulk actions in
> org-agenda, the marks are always lost after the bulk action. Any idea
> why? I am using org (elpa version 20160516) in upstream emacs (compiled
> 2015-12-22).

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda repeated tasks showing multiple times

2016-05-25 Thread Matt Lundin

Paul Harper  writes:

Hello, 

I am getting the following in my org-agenda everyday with 
repeated tasks. 

"Sunday 15 May 2016 
  schedule:   Sched.16x:  Backup KeepassX Local schedule: 
  Sched.16x:  PC Backup to External Drive schedule:   Sched.16x: 
  Review Weekly schedule:   Sched.16x:  Backup KeepassX Local 
 Sunday 15 May 2016 
  schedule:   Sched.16x:  Backup KeepassX Local schedule: 
  Sched.16x:  PC Backup to External Drive schedule:   Sched.16x: 
  Review Weekly schedule:   Sched.16x:  Backup KeepassX Local 
  schedule:   Sched.16x:  PC Backup to External Drive schedule: 
  Sched.16x:  Review Weekly 
And so on 

How do I stop that and only see the task for one particular day 
in my agenda? 



Try setting org-agenda-repeating-timestamp-show-all to nil.

Also, I'm not sure why there are two agendas for "Sunday" shown 
above.  Are you using a custom agenda command? 


Matt



[O] org agenda persistent mark

2016-05-22 Thread Jesse Johnson
Hello!

When I enable persistent marks while performing bulk actions in
org-agenda, the marks are always lost after the bulk action. Any idea
why? I am using org (elpa version 20160516) in upstream emacs (compiled
2015-12-22).

Thanks.

Jesse



[O] org-agenda repeated tasks showing multiple times

2016-05-15 Thread Paul Harper
Hello,

I am getting the following in my org-agenda everyday with repeated
tasks.

"Sunday 15 May 2016
  schedule:   Sched.16x:  Backup KeepassX Local
  schedule:   Sched.16x:  PC Backup to External Drive
  schedule:   Sched.16x:  Review Weekly
  schedule:   Sched.16x:  Backup KeepassX Local
 Sunday 15 May 2016
  schedule:   Sched.16x:  Backup KeepassX Local
  schedule:   Sched.16x:  PC Backup to External Drive
  schedule:   Sched.16x:  Review Weekly
  schedule:   Sched.16x:  Backup KeepassX Local
  schedule:   Sched.16x:  PC Backup to External Drive
  schedule:   Sched.16x:  Review Weekly
And so on

How do I stop that and only see the task for one particular day in my
agenda?

Regards,

Paul




Re: [O] org-agenda-bulk-custom-functions Customize mismatch

2016-05-10 Thread Nicolas Goaziou
Hello,

Phil Hudson  writes:

> The first approach is supported by defcustom and gives us the chance to
> be both more descriptive and more prescriptive. It shouldn't break
> anything that isn't in fact already broken.
>
> The second approach is as simple as changing that `cadr` to a `cdr`, but
> it does risk breaking working configs where the alist was populated
> procedurally.
>
> I propose the first. Here's a patch.

Looks good. Thank you.

Could you send it using "git format-patch". Also, could you provide an
appropriate commit message? See
 for details.

Regards,

-- 
Nicolas Goaziou



[O] org-agenda-bulk-custom-functions Customize mismatch

2016-05-08 Thread Phil Hudson
Another defcustom mismatched with the code.

At line 9962 of org-agenda.el (20160502 release) we have:

  (setq cmd (list (cadr (assoc action org-agenda-bulk-custom-functions)))

This assumes that `org-agenda-bulk-custom-functions` is a
list-of-two-element-lists alist. Thus, the `cadr` form returns (should
return) the second element of one two-element list from the alist.

However, the defcustom is declared as type alist, which in defcustom
means (by default) a list-of-conses alist.

See if you agree with my thinking about this. This means that the code
must always fail if the Customize UI is used to populate
`org-agenda-bulk-custom-functions`. That in turn implies that (to a
first approximation) zero users apart from me have tried to declare a
custom bulk agenda command with its own custom key via Customize. Oh
well.

If my diagnosis is correct, then I see two ways to fix it: either change
the defcustom to create a list-of-two-element-lists alist, or change the
code so that it handles a list-of-conses alist.

The first approach is supported by defcustom and gives us the chance to
be both more descriptive and more prescriptive. It shouldn't break
anything that isn't in fact already broken.

The second approach is as simple as changing that `cadr` to a `cdr`, but
it does risk breaking working configs where the alist was populated
procedurally.

I propose the first. Here's a patch.

-- 
Phil Hudson   http://hudson-it.ddns.net
@UWascalWabbit PGP/GnuPG ID: 0x887DCA63


--- org-20160502/org-agenda.el  2016-05-07 10:18:22.0 +0100
+++ org-mode-mod/org-agenda.el  2016-05-08 14:39:52.0 +0100
@@ -1999,7 +1999,7 @@
 With selected entries in an agenda buffer, `B R' will call
 the custom function `set-category' on the selected entries.
 Note that functions in this alist don't need to be quoted."
-  :type 'alist
+  :type '(alist :key-type character :value-type (group function))
   :version "24.1"
   :group 'org-agenda)
 



Re: [O] org-agenda error

2016-03-15 Thread Peter Salazar
Update: I fixed the org-agenda problem. Turns out the problem was that I'd
created my own custom defun called org-today, and it was interfering with
org-agenda.

The helm-org-in-buffer-headings error is still occurring. Thanks for any
thoughts.

On Tue, Mar 15, 2016 at 7:58 PM, Peter Salazar 
wrote:

> Unfortunately, that's not the case (that helm-org-in-buffer-headings) is
> called in a non-org buffer. It happens whenever I call it from within any
> org-file. I also tried calling it from within a short, minimal org-file
> with just a few headings of various levels, and I get the same error.
>
> The error, once again, is this:
> http://i.imgur.com/FoTiwoq.png
>
> And again, the error I get when I call org-agenda is this:
> http://pastebin.com/wCBgAQLp
>
>
> On Thu, Mar 10, 2016 at 3:21 AM, Nicolas Goaziou 
> wrote:
>
>> Hello,
>>
>> Peter Salazar  writes:
>>
>> > Any thoughts on that? I'm not sure if it's related, but I also get
>> errors
>> > when I try to call helm-org-in-buffer-headings. Somehow the backtrace
>> gets
>> > immediately erased, so here's a screenshot:
>> > http://i.imgur.com/FoTiwoq.png
>>
>> From the above, it looks like `helm-org--get-candidate-in-file' is
>> erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
>> Org, `org-complex-heading-regexp' is nil, hence the result.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>


Re: [O] org-agenda error

2016-03-15 Thread Peter Salazar
Unfortunately, that's not the case (that helm-org-in-buffer-headings) is
called in a non-org buffer. It happens whenever I call it from within any
org-file. I also tried calling it from within a short, minimal org-file
with just a few headings of various levels, and I get the same error.

The error, once again, is this:
http://i.imgur.com/FoTiwoq.png

And again, the error I get when I call org-agenda is this:
http://pastebin.com/wCBgAQLp

On Thu, Mar 10, 2016 at 3:21 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Peter Salazar  writes:
>
> > Any thoughts on that? I'm not sure if it's related, but I also get errors
> > when I try to call helm-org-in-buffer-headings. Somehow the backtrace
> gets
> > immediately erased, so here's a screenshot:
> > http://i.imgur.com/FoTiwoq.png
>
> From the above, it looks like `helm-org--get-candidate-in-file' is
> erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
> Org, `org-complex-heading-regexp' is nil, hence the result.
>
> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] org-agenda error

2016-03-10 Thread Nicolas Goaziou
Hello,

Peter Salazar  writes:

> Any thoughts on that? I'm not sure if it's related, but I also get errors
> when I try to call helm-org-in-buffer-headings. Somehow the backtrace gets
> immediately erased, so here's a screenshot:
> http://i.imgur.com/FoTiwoq.png

>From the above, it looks like `helm-org--get-candidate-in-file' is
erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
Org, `org-complex-heading-regexp' is nil, hence the result.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-agenda error

2016-03-09 Thread Peter Salazar
Any thoughts on that? I'm not sure if it's related, but I also get errors
when I try to call helm-org-in-buffer-headings. Somehow the backtrace gets
immediately erased, so here's a screenshot:
http://i.imgur.com/FoTiwoq.png

On Mon, Mar 7, 2016 at 10:40 AM, Peter Salazar 
wrote:

> Well that's interesting. When I do C-u M-x org-reload and then call
> org-agenda, it displays correctly with no error.
>
> How do I debug? I already went into my config files and commented out all
> the code containing the word org-agenda, but the error still happens.
>
>
> On Mon, Mar 7, 2016 at 6:09 AM, Nicolas Goaziou 
> wrote:
>
>> Hello,
>>
>> Peter Salazar  writes:
>>
>> > I'm suddenly getting "byte-code: Wrong type argument:
>> number-or-marker-p,
>> > nil" when I try to call org-agenda. This happens even when
>> org-agenda-files
>> > is set to nil. Here's the backtrace. Any thoughts on how I can track
>> down
>> > the source of the problem?
>>
>> Could you provide the backtrace running un-compiled Org? It is just
>> a matter of calling C-u M-x org-reload.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>


Re: [O] org-agenda error

2016-03-07 Thread Peter Salazar
Well that's interesting. When I do C-u M-x org-reload and then call
org-agenda, it displays correctly with no error.

How do I debug? I already went into my config files and commented out all
the code containing the word org-agenda, but the error still happens.


On Mon, Mar 7, 2016 at 6:09 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Peter Salazar  writes:
>
> > I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
> > nil" when I try to call org-agenda. This happens even when
> org-agenda-files
> > is set to nil. Here's the backtrace. Any thoughts on how I can track down
> > the source of the problem?
>
> Could you provide the backtrace running un-compiled Org? It is just
> a matter of calling C-u M-x org-reload.
>
> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] org-agenda error

2016-03-07 Thread Nicolas Goaziou
Hello,

Peter Salazar  writes:

> I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
> nil" when I try to call org-agenda. This happens even when org-agenda-files
> is set to nil. Here's the backtrace. Any thoughts on how I can track down
> the source of the problem?

Could you provide the backtrace running un-compiled Org? It is just
a matter of calling C-u M-x org-reload.

Regards,

-- 
Nicolas Goaziou



[O] org-agenda error

2016-03-05 Thread Peter Salazar
Hey everyone,

I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
nil" when I try to call org-agenda. This happens even when org-agenda-files
is set to nil. Here's the backtrace. Any thoughts on how I can track down
the source of the problem?

Thanks!



Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  calendar-gregorian-from-absolute(nil)
  byte-code("\206) \203(\n\203 ;\203\306\307\n
#\202%\n\203$\306\310\n\"\202%\311\206)\f\312\313!\210
\2064@\211;\203B\314\315\316\317
#!\320\321!\210\322\321!\210\323A\206WB\206WC!A\324 D
\206dDE\325AE\"\211F\326=\204{F\327=\205}GG\330\316\331\"\211HIG\203\224F\326W\203\231E\202\277\332\333E!!JGKJKZLEL\334W\203\271\326\202\272\334L\\Z+\211MCN\334OP?QRS\316\211TU\316\211VW\316\211XY\316\211LZ\316\211[\\\316\211]^\316_\335\336`D
\336ADa\257bFS\334cdcdW\203*N@TNBNcT\211c\202*N\237\211N@
]Ne\337e!@)\206B\334T^\340N@
fg\341g!fL*\210\342`fg\341g!fL*\210\343\323A!fg\341g!fL*\210h\204\362N@iNe\337e!@)j\344i!k\344j!l`Tm\203\262\345\346m!\316\347\350$\351\261\210\202\340\352A!\353jiZ\354W\203\333klU\203\321\306\355k\"\202\334\306\356kl#\202\334\357\360\261\210,\361T`S\347\350\362\317F#\210\363T!\210N\211AN\242\211L\203\374\333L!Y`TLDU\211\\\204
Z\204&LEU\203&`Z\2023Z\2033[\2043`[HI\316WI\211AI\242\211X\203N\364\365\215\210\202:n\203i\317o\366\367!\210\370Y!V\371WV\"W)W\204sp\203\362OTOq;\203\211\372q\373Y!\"\202\216qY!\351\261\210\374T`S\347\375Y!$\210\374T`S\362\317$\210\374T`S\376\317$\210\374T`S\377O$\210\\\203\310\374T`S\324\317$\210\201yWF\\#\211W\203\343\201zW\321\"\351\261\210\374T`S\201{L$\210\374T`S\377O$\210\202\362r\203U]\203U\330\316\331\"\346s!\316tu\201|u\201}\"u\201~u\201]#u\201~u\201\200^#u\201~u\201\201\321#u\201\202\201\203u\"\211tc\210+eb\210v\204b\201\204
\210\201\205e!\203r\201\205d!\204\237dSb\210\201\206\201\207!\210\201\205Z\206\211\201\210!\204\237Z\206\225\201\210b\210\201\206\201\210!\210Z\206\247\201\210b\210\361ed\201\211\321\201\212`
AE\201\213b\201\214w\257#\210S\201\215=\203\325\201\216 \210\201\217
\210\317x\201\220\357!.\207" [org-agenda-buffer-tmp-name
org-agenda-sticky org-keys org-match org-agenda-buffer-name start-day
format "*Org Agenda(%s:%s)*" "*Org Agenda(%s)*" "*Org Agenda(a)*"
org-agenda-prepare "Day/Week" time-to-days org-read-date nil t
org-compile-prefix-format agenda org-set-sorting-strategy
org-agenda-ndays-to-span org-today org-agenda-span-to-ndays 7 14
org-agenda-files ifmode calendar-day-of-week
calendar-gregorian-from-absolute 0 org-agenda-list quote last
org-starting-day make-local-variable org-arg-loc org-agenda-current-span
org-days-to-iso-week org-add-props copy-sequence face org-agenda-structure
"\n" org-agenda-span-name "-agenda" 350 " (W%02d)" " (W%02d-W%02d)" ""
":\n" add-text-properties ...] 12)
  org-agenda-list(nil)
  call-interactively(org-agenda-list)
  byte-code("\306 \307 \232\203\310\202\n \311\306\312\313 \"\"\314
\"p@\315\316
!A\306\211BC\306\211DE\306\211FGH\204`\317\320!\203K\204Q\321\322\323\306#\210\306IJ\306\211\223\210K\306\211\223\210\321\324\325\306#\210\321\324\326\306#\210pLM\204\202\327!\211G@MGANO\203\215\330\331M\"H\204\330N\203\330\321\322\323AC#\210N\332=\203\272pIJ\333
\306\223\210K\334
\306\223\210\202\330N\335=\203\330\212pI\336\337!\210J`\306\223\210K\340\337!\306\223\210)\341M
\"\211B\203\342B89\204\364\343\342B8!\203\342B8D\344\345B8!E\346B8FO\203#E;\203\330\347ME#\206\"\330\331M\"\321\324\325F#\210D\350=\2039\351F\352\"\202\237D\353=\203H\351F\354\"\202\237D\355=\203W\351F\356\"\202\237D\357=\203f\351F\360\"\202\237D\361=\203u\351F\362\"\202\237D\363=\203\204\351F\364\"\202\237D\365=\203\223\351F\366\"\202\237D\367=\203\242\351F\370\"\202\237D\371=\203\264\372
\210\351F\373\"\202\237D\374=\203\306\372
\210\351F\375\"\202\237D\376=\203\330\372
\210\351F\377\"\202\237\343D!\203\351\351F\201S\"\202\237\201TD!\203\374\351F\201U\"\202\237\201V\201WD\"\202\237\201XBA@
B\211AA\262\"\202\237M\201Y\232\203-\f\201Z\303!\202\237M\201[\232\203@\201\\\201]!\202\237M\201^\232\203S\201\\\201_!\202\237M\201`\232\203y\201_P\206g\201aPQPR\201\\Q!+\202\237M\201b\232\203\214\201\\\201c!\202\237M\201d\232\203\262\201cP\206\240\201ePQPR\201\\Q!+\202\237M\201f\232\203\305\201\\\201g!\202\237M\201h\232\203\353\201gP\206\331\201iPQPR\201\\Q!+\202\237M\201j\232\203\376\201\\\201k!\202\237M\201l\232\203\201g\306\201m\"\210\201n\201o\201p\337\211$\202\237M\201q\232\203_\201r\201s!\204:\201V\201t!\210N?\205\237\321\322\323AC#\210\201uPPQP

Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-31 Thread Gustav Wikström
Hi Viktor, Kyle

Fair enough. I’m not attached to the refine-function at all. If you like to 
have it removed, then remove it, unless others are of different opinion ofc. 
The functionality is fairly complex, so removing the keybinding might make it 
seem less complicated.

/G

From: Viktor Rosenfeld [mailto:v.rosenf...@gmx.de]
Sent: Saturday, January 30, 2016 00:08
To: emacs-orgmode@gnu.org
Cc: Gustav Wikström ; Kyle Meyer 
Subject: Re: org-agenda-filter-by-tag-refine defaults to exclude

Hi Gustav,

currently, the remove functionality can also be accessed by C-u /. If we want 
to provide a dedicated hotkey, then the following definition will do it:

(add-hook 'org-agenda-mode-hook
  (lambda()
(local-set-key (kbd "\") '(lambda()
(interactive)
(org-agenda-filter-by-tag nil nil 
'exclude
  'append)

I would prefer to remove this function because it doesn’t add functionality. 
Keeping it around just adds another potential source of bugs.

Best,
Viktor

Am 28.01.2016 um 09:27 schrieb Gustav Wikström 
>:

Hi Kyle, Viktor and the group,

I'd say it's a naming-problem. What, really, is the purpose of the function? 
Because applying the proposed change essentially makes the function identical 
to the function it calls. Right? And that function is still available for the 
user, so a "refinement" can be done without the org-agenda-filter-by-tag-refine 
(bound to backslash (\) ) function. As of now, using the function to exclude 
tags in the agenda provides a direct access to that functionality, instead of 
calling org-agenda-filter-by-tag (bound to slash (/) ) plus pushing the minus 
key (-) to switch from filter to exclude.

If you want to make any change, I'd suggest to instead change the name of 
org-agenda-filter-by-tag-refine to org-agenda-filter-by-tag-exclude and to 
leave the code within the function as is (well.. maybe change 'refine to 
'exclude with the same argument as to the function name change).

Best Regards
Gustav

-Original Message-
From: Kyle Meyer [mailto:k...@kyleam.com]
Sent: Tuesday, January 12, 2016 07:19
To: Viktor Rosenfeld >
Cc: emacs-orgmode@gnu.org; Gustav Wikström 
>
Subject: Re: org-agenda-filter-by-tag-refine defaults to exclude

Hi Viktor,

Viktor Rosenfeld > writes:


Hi,

I noticed that org-agenda-filter-by-tag-refine started to exclude
selected tags by default recently because the 'refine in the call to
org-agenda-filter-by-tag is interpreted as an exclude flag.

This seems to have been introduced by 6c6ae99 (org-agenda: Filtering in the 
agenda on grouptags, 2015-01-24).


The attached patch fixes this.

However, it seems that the function is superfluous because
org-agenda-filter-by-tag can filter on multiple tags as well if called
multiple times (that used not to be the case earlier).  So maybe it
should be deprecated and removed?

I agree.  Gustav, does that make sense given your changes in 6c6ae99?


diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index
d91b64d..21928de 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
(defun org-agenda-filter-by-tag-refine (arg  char)
  "Refine the current filter.  See `org-agenda-filter-by-tag'."
  (interactive "P")
-  (org-agenda-filter-by-tag arg char 'refine))
+  (org-agenda-filter-by-tag arg char))


(defun org-agenda-filter-make-matcher (filter type  expand)
  "Create the form that tests a line for agenda filter.  Optional


--
Kyle



Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-29 Thread Viktor Rosenfeld
Hi Gustav,

currently, the remove functionality can also be accessed by C-u /. If we want 
to provide a dedicated hotkey, then the following definition will do it:

(add-hook 'org-agenda-mode-hook
  (lambda()
(local-set-key (kbd "\") '(lambda()
(interactive)
(org-agenda-filter-by-tag nil nil 
'exclude
  'append)

I would prefer to remove this function because it doesn’t add functionality. 
Keeping it around just adds another potential source of bugs.

Best,
Viktor

> Am 28.01.2016 um 09:27 schrieb Gustav Wikström :
> 
> Hi Kyle, Viktor and the group,
> 
> I'd say it's a naming-problem. What, really, is the purpose of the function? 
> Because applying the proposed change essentially makes the function identical 
> to the function it calls. Right? And that function is still available for the 
> user, so a "refinement" can be done without the 
> org-agenda-filter-by-tag-refine (bound to backslash (\) ) function. As of 
> now, using the function to exclude tags in the agenda provides a direct 
> access to that functionality, instead of calling org-agenda-filter-by-tag 
> (bound to slash (/) ) plus pushing the minus key (-) to switch from filter to 
> exclude.
> 
> If you want to make any change, I'd suggest to instead change the name of 
> org-agenda-filter-by-tag-refine to org-agenda-filter-by-tag-exclude and to 
> leave the code within the function as is (well.. maybe change 'refine to 
> 'exclude with the same argument as to the function name change).
> 
> Best Regards
> Gustav
> 
> -Original Message-
> From: Kyle Meyer [mailto:k...@kyleam.com]
> Sent: Tuesday, January 12, 2016 07:19
> To: Viktor Rosenfeld 
> Cc: emacs-orgmode@gnu.org; Gustav Wikström 
> Subject: Re: org-agenda-filter-by-tag-refine defaults to exclude
> 
> Hi Viktor,
> 
> Viktor Rosenfeld  writes:
> 
>> Hi,
>> 
>> I noticed that org-agenda-filter-by-tag-refine started to exclude
>> selected tags by default recently because the 'refine in the call to
>> org-agenda-filter-by-tag is interpreted as an exclude flag.
> 
> This seems to have been introduced by 6c6ae99 (org-agenda: Filtering in the 
> agenda on grouptags, 2015-01-24).
> 
>> The attached patch fixes this.
>> 
>> However, it seems that the function is superfluous because
>> org-agenda-filter-by-tag can filter on multiple tags as well if called
>> multiple times (that used not to be the case earlier).  So maybe it
>> should be deprecated and removed?
> 
> I agree.  Gustav, does that make sense given your changes in 6c6ae99?
> 
>> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index
>> d91b64d..21928de 100644
>> --- a/lisp/org-agenda.el
>> +++ b/lisp/org-agenda.el
>> @@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
>> (defun org-agenda-filter-by-tag-refine (arg  char)
>>   "Refine the current filter.  See `org-agenda-filter-by-tag'."
>>   (interactive "P")
>> -  (org-agenda-filter-by-tag arg char 'refine))
>> +  (org-agenda-filter-by-tag arg char))
> 
>> (defun org-agenda-filter-make-matcher (filter type  expand)
>>   "Create the form that tests a line for agenda filter.  Optional
> 
> 
> --
> Kyle



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-29 Thread Kyle Meyer
Hi Gustav,

Gustav Wikström  writes:

[...]

> If you want to make any change,

Given that, as of 6c6ae99, the function's behavior doesn't match its
name or its previous behavior, I don't think leaving it unchanged is a
good option.

> I'd suggest to instead change the name
> of org-agenda-filter-by-tag-refine to org-agenda-filter-by-tag-exclude
> and to leave the code within the function as is (well.. maybe change
> 'refine to 'exclude with the same argument as to the function name
> change).

Like Viktor, I'm in favor of just removing it, because both its old and
new behavior are easily accomplished with the current
org-agenda-filter-by-tag.

This already made it into a release (v8.3), so in maint I plan to remove
the refine (now exclude) argument from org-agenda-filter-by-tag-refine's
call to org-agenda-filter-by-tag.  I think that gets the function as
close as we can to the old behavior without making any major changes.
In master, I'll just remove org-agenda-filter-by-tag-refine.

I'll make those changes in a few days unless someone objects.

--
Kyle



Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-28 Thread Gustav Wikström
Hi Kyle, Viktor and the group,

I'd say it's a naming-problem. What, really, is the purpose of the function? 
Because applying the proposed change essentially makes the function identical 
to the function it calls. Right? And that function is still available for the 
user, so a "refinement" can be done without the org-agenda-filter-by-tag-refine 
(bound to backslash (\) ) function. As of now, using the function to exclude 
tags in the agenda provides a direct access to that functionality, instead of 
calling org-agenda-filter-by-tag (bound to slash (/) ) plus pushing the minus 
key (-) to switch from filter to exclude.

If you want to make any change, I'd suggest to instead change the name of 
org-agenda-filter-by-tag-refine to org-agenda-filter-by-tag-exclude and to 
leave the code within the function as is (well.. maybe change 'refine to 
'exclude with the same argument as to the function name change).

Best Regards
Gustav

-Original Message-
From: Kyle Meyer [mailto:k...@kyleam.com] 
Sent: Tuesday, January 12, 2016 07:19
To: Viktor Rosenfeld 
Cc: emacs-orgmode@gnu.org; Gustav Wikström 
Subject: Re: org-agenda-filter-by-tag-refine defaults to exclude

Hi Viktor,

Viktor Rosenfeld  writes:

> Hi,
>
> I noticed that org-agenda-filter-by-tag-refine started to exclude 
> selected tags by default recently because the 'refine in the call to 
> org-agenda-filter-by-tag is interpreted as an exclude flag.

This seems to have been introduced by 6c6ae99 (org-agenda: Filtering in the 
agenda on grouptags, 2015-01-24).

> The attached patch fixes this.
>
> However, it seems that the function is superfluous because 
> org-agenda-filter-by-tag can filter on multiple tags as well if called 
> multiple times (that used not to be the case earlier).  So maybe it 
> should be deprecated and removed?

I agree.  Gustav, does that make sense given your changes in 6c6ae99?

> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 
> d91b64d..21928de 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
>  (defun org-agenda-filter-by-tag-refine (arg  char)
>"Refine the current filter.  See `org-agenda-filter-by-tag'."
>(interactive "P")
> -  (org-agenda-filter-by-tag arg char 'refine))
> +  (org-agenda-filter-by-tag arg char))

>  (defun org-agenda-filter-make-matcher (filter type  expand)
>"Create the form that tests a line for agenda filter.  Optional


--
Kyle



Re: [O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-11 Thread Kyle Meyer
Hi Viktor,

Viktor Rosenfeld  writes:

> Hi,
>
> I noticed that org-agenda-filter-by-tag-refine started to exclude
> selected tags by default recently because the 'refine in the call to
> org-agenda-filter-by-tag is interpreted as an exclude flag.

This seems to have been introduced by 6c6ae99 (org-agenda: Filtering in
the agenda on grouptags, 2015-01-24).

> The attached patch fixes this.
>
> However, it seems that the function is superfluous because
> org-agenda-filter-by-tag can filter on multiple tags as well if called
> multiple times (that used not to be the case earlier).  So maybe it
> should be deprecated and removed?

I agree.  Gustav, does that make sense given your changes in 6c6ae99?

> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
> index d91b64d..21928de 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
>  (defun org-agenda-filter-by-tag-refine (arg  char)
>"Refine the current filter.  See `org-agenda-filter-by-tag'."
>(interactive "P")
> -  (org-agenda-filter-by-tag arg char 'refine))
> +  (org-agenda-filter-by-tag arg char))

>  (defun org-agenda-filter-make-matcher (filter type  expand)
>"Create the form that tests a line for agenda filter.  Optional


-- 
Kyle



[O] org-agenda-filter-by-tag-refine defaults to exclude

2016-01-04 Thread Viktor Rosenfeld
Hi,

I noticed that org-agenda-filter-by-tag-refine started to exclude selected tags 
by default recently because the 'refine in the call to org-agenda-filter-by-tag 
is interpreted as an exclude flag. The attached patch fixes this.

However, it seems that the function is superfluous because 
org-agenda-filter-by-tag can filter on multiple tags as well if called multiple 
times (that used not to be the case earlier). So maybe it should be deprecated 
and removed?

Best,
Viktor

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index d91b64d..21928de 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -7580,7 +7580,7 @@ to switch between filtering and excluding."
 (defun org-agenda-filter-by-tag-refine (arg  char)
   "Refine the current filter.  See `org-agenda-filter-by-tag'."
   (interactive "P")
-  (org-agenda-filter-by-tag arg char 'refine))
+  (org-agenda-filter-by-tag arg char))

 (defun org-agenda-filter-make-matcher (filter type  expand)
   "Create the form that tests a line for agenda filter.  Optional



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [O] org-agenda-quit Kills Visible Buffers

2015-12-25 Thread Kyle Meyer
Hi Alan,

Alan Parker Lue  writes:

> After upgrading org-mode recently, I find that hitting "q" for
> (org-agenda-quit) while viewing an agenda kills the buffer that was active
> when I created the agenda.

[...]

> What is going on?

This should be fixed as of 6d0af59 (org-agenda: Don’t kill or bury
non-agenda buffer, 2015-12-24).

http://thread.gmane.org/gmane.emacs.orgmode/103791

-- 
Kyle



[O] org-agenda-quit Kills Visible Buffers

2015-12-24 Thread Alan Parker Lue
After upgrading org-mode recently, I find that hitting "q" for
(org-agenda-quit) while viewing an agenda kills the buffer that was active
when I created the agenda.

I'm on org-mode v8.3.2. To reproduce:

   - Activate a buffer, call it =active_buf.txt=
   - C-c a for (org-agenda)
   - a for "Agenda for current week or day"
   - q for (org-agenda-quit)

I find that =active_buf.txt= has now been killed.

Same thing happens with "x" for (org-agenda-exit). Also happens after
completely doing away with my init.el, so I don't believe this is the
result of a setting.

What is going on?

Alan


[O] org-agenda timetable

2015-11-13 Thread xD
Hi,


I'm new to org mode and I've been playing with it a little enough to see how 
powerful it is. I'm trying to stick to it as much as possible in order to keep 
on learning, but I'm stuck with this one thing I'm struggling right now.


I'm using org-agenda to remind me of what to do, appointments and classes I 
shall give (I'm a school librarist). During the rest of the time, I have to be 
in the library and I shall let peaople know all about itwhen I'm out. I'd like 
to get the information from the org-agenda and display it as a "timetable".



Monday 11/9
Tuesday 11/10
Wednesday 11/11
Thursday 11/12
Friday 11/13

08:00






09:00

appointment w/ local lib.


TODO: coffee

10:00


french class



11:00






…






I've searched in the manual, saw something about exporting data from the agenda 
into a file, but didn't get through anyway. And there must be something better 
than exporting into a file and process that file within Emacs…


So if someone could show me the way, it would be highly appreciated.


regards,

xD

Sent from [ProtonMail](https://protonmail.ch), encrypted email based in 
Switzerland.

Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-29 Thread cesar mena
On Wed, Oct 28, 2015 at 9:52 AM, Nicolas Goaziou  wrote:
> cesar mena  writes:
>
>> however the face is now `org-scheduled-today, as opposed to
>> `org-scheduled-previously, and the agenda sorting is wrong. instead of
>> bubbling to the top (since it is so late) it is staying within the
>> "scheduled today" range.
>
> I committed another attempt in master. Thank you.
>
> Regards,

hi nicolas, list,

everything works. thank you so much.

nice side-effect: the behaviour now allows one to use non "."
repeaters as a poor man's habit mode since the Sched.x header line
will inform one how many cycles are behind.  it's also much clearer.
before on marking as done, the item will just be automatically
rescheduled again with no feedback as to why.

thanks again.

-cm



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-28 Thread Nicolas Goaziou
cesar mena  writes:

> however the face is now `org-scheduled-today, as opposed to
> `org-scheduled-previously, and the agenda sorting is wrong. instead of
> bubbling to the top (since it is so late) it is staying within the
> "scheduled today" range.

I committed another attempt in master. Thank you.

Regards,



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-27 Thread Matt Lundin
cesar mena  writes:

> me again :)
>
> the calculation is correct.
>
> however the face is now `org-scheduled-today, as opposed to
> `org-scheduled-previously, and the agenda sorting is wrong. instead of
> bubbling to the top (since it is so late) it is staying within the
> "scheduled today" range.

I can confirm that overdue .+ tasks now have the org-scheduled-today
face. It seems like they should have org-scheduled-previously (unless
they are habits, of course).

Matt



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-26 Thread cesar mena
hi again nicolas,

sorry. i made a mistake updating my tree.

i'm quite certain i'm on master now "org-version: 8.3.2
(release_8.3.2-219-g770671)" and the repeater resets itself again.

so presently i have a task that looks like this:

** TODO some task
   SCHEDULED: <2015-08-24 Mon ++1w>

and in the agenda it shows up as:

  Scheduled:  TODO some task

best,
-cm





On Mon, Oct 26, 2015 at 9:13 AM, cesar mena  wrote:
> hello guys,
>
> so far so good for me.
>
> thanks nicolas and matt.
>
> -cm
>
> On Sun, Oct 25, 2015 at 1:24 PM, Nicolas Goaziou  
> wrote:
>> Nicolas Goaziou  writes:
>>
>>> Matt Lundin  writes:
>>>
 In short, org-habit seems to want a + notation for the purposes of the
 agenda display and a .+ notation for the purposes of resetting the
 timestamp. What is the best solution?
>>>
>>> Still looking for it.
>>>
>>> Meanwhile, I reverted the opinionated change in
>>> a427098b57c747ecc76feb0593f32922a1e12f67.
>>
>> Another take on this in 3072cb28e8627066f465f1a4af85da88135d0549.



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-26 Thread Nicolas Goaziou
cesar mena  writes:

> sorry. i made a mistake updating my tree.
>
> i'm quite certain i'm on master now "org-version: 8.3.2
> (release_8.3.2-219-g770671)" and the repeater resets itself again.
>
> so presently i have a task that looks like this:
>
> ** TODO some task
>SCHEDULED: <2015-08-24 Mon ++1w>
>
> and in the agenda it shows up as:
>
>   Scheduled:  TODO some task

Hopefully fixed, this time. Thank you.

Regards,



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-26 Thread cesar mena
me again :)

the calculation is correct.

however the face is now `org-scheduled-today, as opposed to
`org-scheduled-previously, and the agenda sorting is wrong. instead of
bubbling to the top (since it is so late) it is staying within the
"scheduled today" range.


best,
-cm


On Mon, Oct 26, 2015 at 4:31 PM, Nicolas Goaziou  wrote:
> cesar mena  writes:
>
>> sorry. i made a mistake updating my tree.
>>
>> i'm quite certain i'm on master now "org-version: 8.3.2
>> (release_8.3.2-219-g770671)" and the repeater resets itself again.
>>
>> so presently i have a task that looks like this:
>>
>> ** TODO some task
>>SCHEDULED: <2015-08-24 Mon ++1w>
>>
>> and in the agenda it shows up as:
>>
>>   Scheduled:  TODO some task
>
> Hopefully fixed, this time. Thank you.
>
> Regards,



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-26 Thread cesar mena
hi samuel,

yes i suspect this is why it hasn't been reported in years.

what say you nicolas?

-cm

On Mon, Oct 26, 2015 at 4:23 PM, Samuel Wales  wrote:
> fwiw, i am one who is so [disorganized?] that the old behavior is
> preferred.  if something is a 6m repeater, and i ignore it for 6m,
> it's actually useful to be reminded after another repeat.  perhaps
> more normal people would understand 1w.  no matter how much i "should"
> mootify it or take it off the list or do it, this "bug" has proved
> useful in practice.
>
> i don't claim to represent hordes of disorganized people, but there you have 
> it.



Re: [O] org-agenda-scheduled-leaders and repeating tasks

2015-10-26 Thread Samuel Wales
fwiw, i am one who is so [disorganized?] that the old behavior is
preferred.  if something is a 6m repeater, and i ignore it for 6m,
it's actually useful to be reminded after another repeat.  perhaps
more normal people would understand 1w.  no matter how much i "should"
mootify it or take it off the list or do it, this "bug" has proved
useful in practice.

i don't claim to represent hordes of disorganized people, but there you have it.



  1   2   3   4   >