[O] Sorting Todo

2016-12-04 Thread marvin doyley
Dear All,
I would like to sort my TODO file using two criteria: (a) priority and (b) 
schedule and deadline.
I would like items to be ordered as follows - priority, deadline, schedule, and 
everything else.
Does anybody know how to do this ?

Cheers,
M


Re: [O] [bug] timed repeater shows up in wrong place

2016-12-04 Thread Samuel Wales
On 12/3/16, Nicolas Goaziou  wrote:
> Anyway, I pushed a change to maint that should solve the "72x vs. 2x"
> issue.

thank you!

i am glad i do not have to switch to master to get 2x.

> I implemented the following variables in master:
>
> - `org-agenda-show-future-repeats'
> - `org-agenda-prefer-last-repeat'
>
> and removed `org-agenda-repeating-timestamp-show-all', which was
> ambiguous.

> Feedback welcome.

the only difference i found between 8 and 9maint, running today, with
show all set to nil, is:

  SCHEDULED: <2016-10-17 Mon .+7d>

which shows today as 7x and tomorrow in 9maint, but only tomorrow in
8.  presumably 8 considers the 7x a duplicate but 9 does not.

with the new variables in master, i found that master is the same as 8.

thus, master can be set to be exactly like 8, while maint is slightly different.

===

i think the variables and names and docstrings are very good.

the only feature that seems to be missing from 8 and 9maint that might
be needed in 9master is a list of strings for todo kw that should show
future repeats.  thus you could say that NOTE does not show future
repeats, but NEXTREPEAT does.



Re: [O] capitalization of titles in org-ref

2016-12-04 Thread Georg W. Otto
John Kitchin  writes:

> you could try commenting out orcb-key too. it should be using the
> bibtex-autokey settings though.
>

If I do that, the key is omitted altogether. I did some further
searching and testing, and I came to the conclusion that the autokey
generator ignores all non-capitalized words in its default setting

(defcustom bibtex-autokey-titleword-ignore
  '("A" "An" "On" "The" "Eine?" "Der" "Die" "Das"
"[^A-Z].*" ".*[^a-zA-Z0-9].*")

so in my init file I set it like this:

(setq bibtex-autokey-titleword-ignore '("A" "An" "On" "The" "of"))

Now it works the way I want it.

Thanks for your help.

Georg

-- 
Georg Otto
The UCL Institute of Child Health




Re: [O] Multiple underscores crash org latex export; other exporters survive

2016-12-04 Thread Scott Randby
On 12/04/2016 05:13 AM, Nicolas Goaziou wrote:
> Scott Randby  writes:
> 
>> There is an interesting issue here. I sometimes want to use ~ in a code
>> snippet, so I can't use ~code snippet~. Yet,
> 
> Indeed, this was discussed in this ML. We need some escape character in
> Org. A general escape character is a bit ambitious, and not necessarily
> useful, but we could introduce one specifically for verbatim and code
> markers, much like in macros and verbatim blocks, e.g.
> 
>   ~some\~code\=with special\\ characters~
> 
> There is a design decision involved: what character can be escaped? It
> could be anything, or limit to "~" for code and "=" for verbatim
> markers. For example macros limit escape-able characters to "," and "\".
> This makes the contents easier to read, but the rule is inconsistent.
> 
> Thoughts?

I don't think I have a good enough technical understanding of the issue
to provide constructive thoughts. I've adapted to using Org markup when
it works and specifying literal LaTeX when necessary. I don't need to
specify literal LaTeX very often anyway.

>> I've wondered why \verb isn't exported correctly without specifying it
>> as literal LaTeX,
> 
> It's because Org recognize LaTeX commands only if they are followed by
> a blank character, the end of buffer, or "{}", which is not the case
> with \verb@...@.

Now I understand. Thanks.

Scott



Re: [O] [Patch v2] Add support for sqsh sql src blocks

2016-12-04 Thread Sebastien Vauban
Hello all,

A quick question: does someone has a link to a working executable on
Windows (with or without Cygwin).  I have searched recently, but found
nothing, or not-working exe.

A pity it's not available in Cygwin packages...

Thanks in advance.

-- 
Sebastien Vauban




Re: [O] [bug] timed repeater shows up in wrong place

2016-12-04 Thread cesar mena
Nicolas Goaziou  writes:

> Hello,
>
> cesar mena  writes:
>
>> just making sure i'm getting this.
>>
>> in maint, if org-agenda-repeating-timestamp-show-all is nil we get
>> 72x. if it is non nil we get 2x. i'm in the 72x camp, so i don't need to
>> do anything.
>
> It is the opposite. 
>
>   `org-agenda-repeating-timestamp-show-all' t   -> 72x
>   `org-agenda-repeating-timestamp-show-all' nil -> 2x
>
> Default value is t, so you don't need to do anything.
>
>> when master comes around org-agenda-repeating-timestamp-show-all will go
>> away. to get 72x make sure that org-agenda-prefer-last-repeat is nil (?)
>
> 72x is the default behaviour in both maint and master. IOW
> `org-agenda-prefer-last-repeat' is nil by default in master.
>
> Regards,
>
> -- 
> Nicolas Goaziou

ok; this is perfect, whilst allowing users to keep the org 8 (2x)
behaviour.

thank you again nicolas.

-cm



Re: [O] Multiple underscores crash org latex export; other exporters survive

2016-12-04 Thread Nicolas Goaziou
Hello,

Scott Randby  writes:

> There is an interesting issue here. I sometimes want to use ~ in a code
> snippet, so I can't use ~code snippet~. Yet,

Indeed, this was discussed in this ML. We need some escape character in
Org. A general escape character is a bit ambitious, and not necessarily
useful, but we could introduce one specifically for verbatim and code
markers, much like in macros and verbatim blocks, e.g.

  ~some\~code\=with special\\ characters~

There is a design decision involved: what character can be escaped? It
could be anything, or limit to "~" for code and "=" for verbatim
markers. For example macros limit escape-able characters to "," and "\".
This makes the contents easier to read, but the rule is inconsistent.

Thoughts?

> Org code: \verb@a_variable_deleteThisAndItWorks@
>
> Exported LaTeX: \verb@a\(_{\text{variable}}_{\text{deleteThisAndItWorks}}\)@
>
> The exported LaTeX is not what we want. Instead,
>
> Org code: #+latex:\verb@a_variable_deleteThisAndItWorks@
>
> Alternative: @@latex:\verb@a_variable_deleteThisAndItWorks@@@
>
> Exported LaTeX: \verb@a_variable_deleteThisAndItWorks@
>
> I've wondered why \verb isn't exported correctly without specifying it
> as literal LaTeX,

It's because Org recognize LaTeX commands only if they are followed by
a blank character, the end of buffer, or "{}", which is not the case
with \verb@...@.

Regards,

-- 
Nicolas Goaziou



Re: [O] [bug] timed repeater shows up in wrong place

2016-12-04 Thread Nicolas Goaziou
Hello,

cesar mena  writes:

> just making sure i'm getting this.
>
> in maint, if org-agenda-repeating-timestamp-show-all is nil we get
> 72x. if it is non nil we get 2x. i'm in the 72x camp, so i don't need to
> do anything.

It is the opposite. 

  `org-agenda-repeating-timestamp-show-all' t   -> 72x
  `org-agenda-repeating-timestamp-show-all' nil -> 2x

Default value is t, so you don't need to do anything.

> when master comes around org-agenda-repeating-timestamp-show-all will go
> away. to get 72x make sure that org-agenda-prefer-last-repeat is nil (?)

72x is the default behaviour in both maint and master. IOW
`org-agenda-prefer-last-repeat' is nil by default in master.

Regards,

-- 
Nicolas Goaziou