Re: org-agenda todos list sorted by earliest deadline first

[Sébastien Gendre]

My Emacs version is 27.2 and Org is 9.4.4.

The value of "org-agenda-sorting-strategy" is:

((agenda habit-down time-up priority-down category-keep)
 (todo priority-down category-keep deadline-up)
 (tags priority-down category-keep deadline-up)
 (search category-keep))

Le 2 avril 2022 23:16:23 GMT+02:00, Samuel Wales  a écrit 
:
>perhaps try including your code and the emacs and org versins.  i
>think there have been recentish changes insorting strategy.
>
>might also try paradoxically deadline-down etc.
>
>On 4/2/22, Sébastien Gendre  wrote:
>> Hello.
>>
>> In org-agenda, for the todos list, I try to have tasks with deadlines at
>> top. With earliest deadline first.
>>
>> But, when I customize the variable "org-agenda-sorting-strategy" by adding
>> "deadline-up" for "todo" and "tags", it has no effect.
>>
>> Any advice ?
>
>
>-- 
>The Kafka Pandemic
>
>A blog about science, health, human rights, and misopathy:
>https://thekafkapandemic.blogspot.com

[BUG] sparse tree using property name with hyphen not recognised [9.5.2 (release_9.5.2-401-g91681f)]

[Zhuhui Lam]

When doing a sparse tree using a property named with a hyphen (e.g.
word-word2)
this is not found/recognised. Instead if the property is  named with an
underscore (e.g. word_word2) the sparse tree works as expected.

Emacs  : GNU Emacs 28.0.92 (build 2, x86_64-w64-mingw32)
 of 2022-03-24
Package: Org mode version 9.5.2 (release_9.5.2-401-g91681f )

Re: org-agenda todos list sorted by earliest deadline first

[Samuel Wales]

perhaps try including your code and the emacs and org versins.  i
think there have been recentish changes insorting strategy.

might also try paradoxically deadline-down etc.

On 4/2/22, Sébastien Gendre  wrote:
> Hello.
>
> In org-agenda, for the todos list, I try to have tasks with deadlines at
> top. With earliest deadline first.
>
> But, when I customize the variable "org-agenda-sorting-strategy" by adding
> "deadline-up" for "todo" and "tags", it has no effect.
>
> Any advice ?


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

org-agenda todos list sorted by earliest deadline first

[Sébastien Gendre]

Hello.

In org-agenda, for the todos list, I try to have tasks with deadlines at top. 
With earliest deadline first.

But, when I customize the variable "org-agenda-sorting-strategy" by adding 
"deadline-up" for "todo" and "tags", it has no effect. 

Any advice ?

Re: org-cite and text/Unicode export

[Bruce D'Arcus]

On Sat, Apr 2, 2022 at 10:50 AM Max Nikulin  wrote:

> I am unsure to what degree it is Org issue, it may be partially
> citeproc.el or CSL style issues.

One quick way to narrow this down is to run it through pandoc, which
supports org-cite.

It uses a different, haskell-based, CSL processor.

Bruce

org-cite and text/Unicode export

[Max Nikulin]

Hi.

I spent some time playing with org-cite just to get some impression and 
I noticed some issues with plain text export. The only reason why I used 
text is that it is fast and the result contains no additional markup 
like for LaTeX or HTML buffers. Since it was a test example rather than 
a real life use case, it is low priority issue and perhaps may be ignored.


I am unsure to what degree it is Org issue, it may be partially 
citeproc.el or CSL style issues.


--- >8 ---
A citation [1].

[1] A. L. Schawlow and C. H. Townes, [“Infrared and optical masers,]”
/Phys. rev./, vol. 112, pp. 1940–1949, Dec. 1958.


[“Infrared and optical masers,]

--- 8< ---

- No "Bibliography" (or "References") section
- Emphasis markers "/Phys. rev./"
- Hyperlink outside of the bibliography entry, it is partially due to 
CSL style selection, for e.g. american-physics-society.csl result is better.
- Rather strange hyperlink marker including opening quote and trailing 
comma, but not closing quote character.


With annales.csl the result looks even more strange, but it is footnote 
style, so it is unlikely suitable for plain text export.


Source file:
--- >8 ---
#+options: toc:nil
#+bibliography: obt.bib
#+cite_export: csl ieee.csl

A citation [cite:@schawlow1958iao].

#+print_bibliography:

# Local Variables:
# org-cite-csl-styles-dir: "/usr/share/citation-style-language/styles"
# End:
--- 8< ---

obt.bib file:
--- >8 ---
@ARTICLE{schawlow1958iao,
  author = {Schawlow, Arthur Leonard and Townes, Charles Hard},
  title = {Infrared and Optical Masers},
  journal = {Phys. Rev.},
  year = {1958},
  volume = {112},
  pages = {1940--1949},
  month = {Dec},
  doi = {10.1103/PhysRev.112.1940},
  issue = {6},
  publisher = {American Physical Society},
}
--- 8< ---

org-cite, CSL styles and space before citation

[Max Nikulin]

On 01/04/2022 00:27, Bruce D'Arcus wrote:

On Thu, Mar 31, 2022 at 11:27 AM Max Nikulin wrote:


Emphasis and bold markers may appear in plain text export. Behavior of styles is
not uniform in respect to adding (unbreakable?) space before citation.


Sorry; not following here again. Isn't the space before a citation
determined by the user?


I was lucky enough to pick a couple of styles having different behavior.
Notice additional unbreakable space before "[1]" in the second example.
I have checked a couple of IEEE papers and they have spaces before
citations, so to switch from IEEE to APS style it is necessary to remove
spaces before citations.


The latter style includes a non-breaking space in the citation definition ...

https://github.com/citation-style-language/styles/blob/21e2177295be5b98ef49b00dd4b8cc7e68d2143d/american-physics-society.csl#L96

... which strikes me as odd, though would explain what you see.


I grepped the directory with CSL styles for "prefix" and tried 
annales.csl. It removes regular spaces before citations (if they exist) 
but preserves non-breakable one.


Since the project has enormous amount of styles, it is hard to ensure 
that they have uniform quality and behavior e.g. in respect to 
responsibility for a space before citations. A test sample and result of 
rendering for it with a check list for style authors may help, but they 
will evolve in time. It is unlikely that accidental contributors of 
styles will manage to maintain compliance to current edition of tests. 
However it would be great for various tools dealing with styles.


P.S. After all, it is necessary to change style when e.g. a journal 
declined a paper. It may mean that the quality of the paper is not high 
enough. Adjusting the text for another style is a burden that makes it 
harder to just send it to another journal and thus reduces number of low 
quality papers. And such efforts are negligible in comparison with 
attempts to mane the content better. So some oddities with particular 
styles are not a serious issue.

Re: TOC and latex memoir class

[Juan Manuel Macías]

Hi Steve,

Steve Downey writes:

> In order to place the table of contents without a section name
> "Contents" the memoir class uses \tableofcontents* rather than
> \tableofcontents.
> However, `org-latex-toc-command` is documented as:
>   "LaTeX command to set the table of contents, list of figures, etc.
> This command only applies to the table of contents generated with
> the toc:nil option, not to those generated with #+TOC keyword."
> Which is confusing in two ways, first that toc:nil doesn't generate a
> table of contents, and that it doesn't seem to provide any way of
> getting the string to be used? 
>
> As a workaround, I could use the latex command directly, but that
> means not having it available in, for example, an html export. 
>
> Is there a workaround I'm missing? 

One possible workaround would be to define a macro with a conditional:
if exporting to LaTeX, returns the string 'toc:nil'; otherwise, returns
'toc:t'. And the LaTeX command can be added via a export snippet.
Something like this:

#+MACRO: mytoc (eval (if (eq org-export-current-backend 'latex) "#+OPTIONS: 
toc:nil" "#+OPTIONS: toc:t"))

{{{mytoc}}}

@@latex:\tableofcontents*@@

* Heading 1

lorem ipsum dolor

* Heading 2

lorem ipsum dolor



Best regards,

Juan Manuel