Re: [BUG] @* in [cite/nocite:@*] is a valid special LaTeX bibliography key, but it is highlighted using "error" face by oc.el (was: [PATCH] oc-csl: Add support for nocite citations)

Dear All, On Sun, 3 Jul 2022 at 15:09, Ihor Radchenko wrote: > Then, oc-natbib, oc-biblatex, and oc-csl should be modified to provide > an alternative activation function that will not highlight @* as > non-existing key. > > Probably, we can even use an alternative "special" key face, not > 'org

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

Hello All, I’ve been viewing this thread with trepidation for a while, and I’ve reached a point where I feel compelled to add another 2c of mine. > It’s about the GNU Project’s moral stand (nonfree software is an > injustice, and encouraging people to use it is wrong), and what > follows from tha

Re: [more absurd]

>writes: > On Mon, Jul 04, 2022 at 07:10:27AM +0200, Uwe Brauer wrote: > [...] >> That really su... (My use case only concerned numbers from 0-10). >> >> So it boils down to the question: why isn't 0 considered as >> natural numbers, as, according to the Peano ax

Re: [more absurd]

On Mon, Jul 04, 2022 at 07:10:27AM +0200, Uwe Brauer wrote: [...] > That really su... (My use case only concerned numbers from 0-10). > > So it boils down to the question: why isn't 0 considered as natural numbers, > as, according to the Peano axioms, it is? I don't know whether you're serious

Re: [more absurd]

>>>writes: > On Sun, Jul 03, 2022 at 10:24:34PM +0200, Uwe Brauer wrote: >> >>> "BB" == Bruno Barbier writes: >> >> > Uwe Brauer writes: >> >> >> >> I am confused what is 02 supposed to mean? >> >> > That's a leading 0 digit, that can be ignored. >> >> >(string-to-number "02") => 2 >

Re: [more absurd]

On Sun, Jul 03, 2022 at 10:24:34PM +0200, Uwe Brauer wrote: > >>> "BB" == Bruno Barbier writes: > > > Uwe Brauer writes: > >> > >> I am confused what is 02 supposed to mean? > > > That's a leading 0 digit, that can be ignored. > > >(string-to-number "02") => 2 > > > Alphabetical sorting

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I don't see this discussion leading to anything if it is only about > personal

Re: [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

Hi Ihor, Two comments on this: > The inline src block defaults should probably be documented. See > > Patches are welcome. I think it would also be nice if one could set inline header args with `#+properties' and `:PROPERTIES:' in the same mann

Re: [BUG] wrapping links

Tor Kringeland writes: > When a link goes over a (real) line wrap for indented lines, the leading > spaces get formatted as part of the link and this looks ugly. > > #+begin_example > - [[this link looks > ugly]] > #+end_example > > It would be nice to at least have an option to disable formatt

Re: [BUG] formatting at edges of link

Tor Kringeland writes: > For example > > [[normal /italic/ normal]] > > formats correctly as a link, but > > [[/italic/]] > > doesn't format to italic. A workaround is to write > > /[[italic]]/ > > but sometimes the formatting is part of my link names, so it's a bit > annoying to reformat

[BUG] wrapping links

When a link goes over a (real) line wrap for indented lines, the leading spaces get formatted as part of the link and this looks ugly. #+begin_example - [[this link looks ugly]] #+end_example It would be nice to at least have an option to disable formatting of the leading (and trailing) spaces.

[BUG] formatting at edges of link

For example [[normal /italic/ normal]] formats correctly as a link, but [[/italic/]] doesn't format to italic. A workaround is to write /[[italic]]/ but sometimes the formatting is part of my link names, so it's a bit annoying to reformat to get correct formatting.

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

Jean Louis writes: > On 2022-06-20 04:22, Ihor Radchenko wrote: >> Cryptocurrencies are easier in terms of software freedom, but their >> legal status is not stable (e.g. cryptocurrency is illegal in the >> country I now live in). > > Are you sure? Look at this here: > https://www.cnbc.com/2022/0

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

On 2022-06-20 04:22, Ihor Radchenko wrote: Cryptocurrencies are easier in terms of software freedom, but their legal status is not stable (e.g. cryptocurrency is illegal in the country I now live in). Are you sure? Look at this here: https://www.cnbc.com/2022/03/17/ukraine-legalizes-cryptocurre

Imposible to set :weight Light for a font

Hi Another noob X file: I can't set ":weight Light" for a font. If I set it using the "Menu, Options, Set Default font, Cascadia Mono - style Light"; the text in the buffer changes correctly; https://i.postimg.cc/htZ4rL2w/1.jpg but in the init.el the :family changes into "Cascadia Mono Lig

Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

Max Nikulin writes: >> > I noticed that the Org documentation server gives 404 Not Found for a > large number of links published all over the internet because (1) it > parses URLs case-sensitively and (2) the case has changed at some point. > I stumble upon such 404s errors dai

Re: [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

Hi Rudolf, as to your question when to use an inline src block: I use it particularly in documents that present results from data sets. For instance, when you calculate something (e.g., an average value), you can store it in a variable =foo= (e.g., in R, python etc., just make sure you use the

Re: [more absurd]

>>> "BB" == Bruno Barbier writes: > Uwe Brauer writes: >> >> I am confused what is 02 supposed to mean? > That's a leading 0 digit, that can be ignored. >(string-to-number "02") => 2 > Alphabetical sorting will see the "0" though and sorts differently. But 02 seems to me a wired mathema

Re: [more absurd]

Uwe Brauer writes: > > I am confused what is 02 supposed to mean? That's a leading 0 digit, that can be ignored. (string-to-number "02") => 2 Alphabetical sorting will see the "0" though and sorts differently. Bruno

Re: [more absurd]

>>> "BB" == Bruno Barbier writes: > Uwe Brauer writes: >> >> I am confused: >> >> https://en.wikipedia.org/wiki/Natural_number >> >> States that Some definitions, including the standard ISO >> 8-2,[3][a] begin the natural numbers with 0, so I thought this is >> standard emacs/org uses.

Re: [more absurd]

Uwe Brauer writes: > > I am confused: > > https://en.wikipedia.org/wiki/Natural_number > > States that Some definitions, including the standard ISO > 8-2,[3][a] begin the natural numbers with 0, so I thought this is > standard emacs/org uses. I don't know, sorry. > This seems not to be the

Re: [more absurd]

>>> "BB" == Bruno Barbier writes: > Uwe Brauer writes: >> Consider >> >> | 2 | >> | 1 | >> | 1 | >> | 0 | >> | | >> | | >> >> (org-table-sort-lines nil nil nil nil t) (numerically 'n' gives) > ... >> >> So no empty lines, what the hell is going on here? > The reason is probably that t

Re: [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

Ihor Radchenko writes: > […] By default, unlike ordinary src blocks, inline src blocks are > only exported as results - code is not exported, only the result is > exported. […] Further, because Org is not always able to evaluate > src blocks (when the relevant ob-*.el is not loaded), inline sr

Re: [more absurd] (was: org-table-sort-lines (numerically) leaves 0 separated)

Uwe Brauer writes: > Consider > > | 2 | > | 1 | > | 1 | > | 0 | > | | > | | > > (org-table-sort-lines nil nil nil nil t) (numerically 'n' gives) ... > > So no empty lines, what the hell is going on here? The reason is probably that the function 'string-to-number' return 0 for anything th

[more absurd] (was: org-table-sort-lines (numerically) leaves 0 separated)

>>> "UB" == Uwe Brauer writes: > Hi > I have the following table > | name | marks | > |---+---| > | Auser | 0.5 | > | Buser | 2 | > | Cuser | 0 | > | Duser | 2 | > | Euser | 0 | > | Fuser | 3 | > | Guser | | > | Huser | 0 | > | Iuser | | > | Juser |

Re: [BUG] org-auto-repeat-maybe: error "Can’t expand minibuffer to full frame" and missing log note

On Fri, 1 Jul 2022 at 07:43, Ihor Radchenko wrote: > > Currently, when we call `org-auto-repeat-maybe', it adds > > `org-add-log-note' to post-command-hook using `org-add-log-setup'. As > > soon as we reach the question about 10 repeater intervals (the call to > > `y-or-n-p' from `org-auto-repeat-

Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

I noticed that the Org documentation server gives 404 Not Found for a large number of links published all over the internet because (1) it parses URLs case-sensitively and (2) the case has changed at some point. I stumble upon such 404s errors daily. See, for instance, the link to Column Groups

Re: Proposal: 'executable' org-capture-templaes

Max Nikulin writes: > On 21/06/2022 14:37, Arthur Miller wrote: >> Emacs as a whole is not designed to work in the way I >> percieve it has clean separation between contexts in each frame. Menu >> buffer is "global" for entire Emacs process, and there are other >> features of Emacs that does not

Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

Tim Cross writes: >>> I noticed that the Org documentation server gives 404 Not Found for a >>> large number of links published all over the internet because (1) it >>> parses URLs case-sensitively and (2) the case has changed at some point. >>> I stumble upon such 404s errors daily. See, for in

Re: Org links and Flatpak firefox

Hi Max, Thanks for the debugging suggestions. It helped me figure out that the problem was us usual human error. Emacs opens URLs in the last-active (from the UI perspective) firefox, even if there is a firefox on the current virtual desktop. I had "browse-url-generic-program" set to a script

[BUG] @* in [cite/nocite:@*] is a valid special LaTeX bibliography key, but it is highlighted using "error" face by oc.el (was: [PATCH] oc-csl: Add support for nocite citations)

John Kitchin writes: > It is a special command. See > > https://texfaq.org/FAQ-nocitestar > > It is used to put all entries in a bibtex file in the bibliography. > > Here is a minimal example Tex file that should list all the entries in > mybibliography.bib > > \documentstyle{article} > \begin{do

Re: [PATCH] oc-csl: Add support for nocite citations

It is a special command. See https://texfaq.org/FAQ-nocitestar It is used to put all entries in a bibtex file in the bibliography. Here is a minimal example Tex file that should list all the entries in mybibliography.bib \documentstyle{article} \begin{document} \nocite{*} \bibliographystyle{uns

Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

Ihor Radchenko writes: > Rudolf Adamkovič writes: > >> I noticed that the Org documentation server gives 404 Not Found for a >> large number of links published all over the internet because (1) it >> parses URLs case-sensitively and (2) the case has changed at some point. >> I stumble upon suc

Re: [PATCH] oc-csl: Add support for nocite citations

I don't know the internals, I just know it works from org, though I'm not near a computer ATM. On Sun, Jul 3, 2022, 8:34 AM Ihor Radchenko wrote: > "Bruce D'Arcus" writes: > > > Ihor - on *, he is bringing oc-csl in line with the oc-natbib and > > oc-biblatex processors. > > I am sorry, but I s

Re: [PATCH] oc-csl: Add support for nocite citations

"Bruce D'Arcus" writes: > Ihor - on *, he is bringing oc-csl in line with the oc-natbib and > oc-biblatex processors. I am sorry, but I still do not understand. AFAIK, \nocite{*} is not a valid LaTeX command. Best, Ihor

Re: [PATCH] oc-csl: Add support for nocite citations

Ihor - on *, he is bringing oc-csl in line with the oc-natbib and oc-biblatex processors. On Sun, Jul 3, 2022, 7:57 AM Ihor Radchenko wrote: > András Simonyi writes: > > >> By "*", do you mean something like [cite/n:@*]? > >> If so, will it be correctly fontified as an existing citation? > > >

Re: [PATCH] oc-csl: Add support for nocite citations

András Simonyi writes: >> By "*", do you mean something like [cite/n:@*]? >> If so, will it be correctly fontified as an existing citation? > > ... As for fontification, this is a very good > question! I've checked it now with the built-in "basic" > activation processor and it shows the "*" with

Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

Rudolf Adamkovič writes: > I noticed that the Org documentation server gives 404 Not Found for a > large number of links published all over the internet because (1) it > parses URLs case-sensitively and (2) the case has changed at some point. > I stumble upon such 404s errors daily. See, for ins

Re: [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

Rudolf Adamkovič writes: > the documentation at > > https://orgmode.org/manual/Structure-of-Code-Blocks.html > > says > > "Org offers two ways to structure source code in Org documents: in a > source code block, and directly inline. Both specifications are shown > below." > > and > > "An inline c

Re: [BUG] inline src_lang code is not fontified on headline

"Christopher M. Miles" writes: > The src_lang code fontification is normal in content, but not correctly > fontified on headline. > > There is a screenshot in attachment. Thanks for reporting! Note that a major rewrite of Org fontification is WIP. See https://orgmode.org/list/87ee7c9quk.fsf@loca

[BUG] inline src_lang code is not fontified on headline

The src_lang code fontification is normal in content, but not correctly fontified on headline. There is a screenshot in attachment. I'm using latest HEAD commit (0ed0dea229a3) of Org Mode source code. -- [ stardiviner ] I try to make every word tell the meaning that I want to express.

[BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ )]

Hello again! I noticed that the Org documentation server gives 404 Not Found for a large number of links published all over the internet because (1) it parses URLs case-sensitively and (2) the case has changed at some point. I stumble upon such 404s errors daily. See, for instance, the link to Co

[BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

Hello folks, the documentation at https://orgmode.org/manual/Structure-of-Code-Blocks.html says "Org offers two ways to structure source code in Org documents: in a source code block, and directly inline. Both specifications are shown below." and "An inline code block conforms to this structu

Re: Clocktable parameters

> Ihor Radchenko writes: > Colin Baxter 😺️ writes: >> I find the differences between the variables >> >> (1) org-clocktable-defaults (2) >> org-agenda-clockreport-parameter-plist >> >> hard to understand. >> >> Ok, (1) seems reasonably clear. It's descr