Re: Why not org-tempo insert upcased strings?

[Kyle Meyer]

Kaushal Modi  writes:

> On Mon, Apr 27, 2020, 4:35 AM tsuucat  wrote:
>
>> Why the convention is changed in org-tempo?
>
> I'm a bit hazy about this, but I believe that org-tempo got introduced
> after this commit:
> https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0

org-tempo was added in 94f1a5843 (org-tempo.el: New file for expansion
of templates, 2017-12-05) and already existed at the time of that
commit, 13424336a (org-element: Prefer lower case letters for blocks and
keywords, 2018-01-24).

  $ git ls-tree -r 13424336a6f30c50952d291e7a82906c1210daf0 | grep tempo
  100644 blob 38d21de5e15b8fed0ac0a2b7737064e2a7842350  lisp/org-tempo.el
  100644 blob 20062feebe108a0cb9a32f2bf9bb6fdd03924833  
testing/lisp/test-org-tempo.el

> This was a few years ago. There was even a discussion thread on this list
> that showed preference to make that change.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2017-10/msg00449.html

I'm just a passive observer, but I agree that that message
(87r2tmwcrv@nicolasgoaziou.fr) is probably the key one to point to.
It belongs to the thread that led to c04e357f3 (Replace easy templates
with org-insert-structure-template, 2017-11-05).  At that point, the
upper-case-inserting easy templates were replaced by the
lower-case-inserting org-insert-structure-template command.

Shortly after, Rasmus introduced org-tempo
(https://yhetil.org/orgmode/87mv2ya2ep@pank.eu/), which restored the
ability for easy-template-like "

Re: Specifying the execution function and/or nested major mode for babel blocks

[Kyle Meyer]

Vladimir Nikishkin  writes:

>>> (add-to-list 'org-src-lang-modes '("f90" . fortran))
>
> Language alignment is fine. What needs to be done is to make org-babel
> use org-babel-execute:fortran for both begin_src fortran, and for
> begin_src f90.

Yeah, my suggestion doesn't make sense given you said there is a
f90-mode.  Try two:

  (org-babel-make-language-alias "f90" "fortran")

Assuming that works for you and is expected to work generally, it'd be
good to add that to ob-fortran.el.

Re: Why not org-tempo insert upcased strings?

[Kaushal Modi]

On Mon, Apr 27, 2020, 4:35 AM tsuucat  wrote:

>
> > tsuucat  writes:
> >
> >>> Yes, the convention is now to have downcased keywords.
> >> Thanks. Is the convention documented?
> >>
> >> https://orgmode.org/manual/Structure-Templates.html#Structure-Templates
> 
> >> It doesn’t seems that The Org Manual uses such a convention.
> >
> > While the manual doesn't recommend which you should prefer (I don't
> > think), it does provide a rationale for its use of uppercase:
> >
> >(info "(org)Conventions")
> >
>
> Hmm…
> According to etc/ORG-NEWS, org-tempo.el was introduced in Org 9.2.
> Unfortunately the section doesn’t refer the change of convention.
>
> Why the convention is changed in org-tempo?
>

I'm a bit hazy about this, but I believe that org-tempo got introduced
after this commit:
https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0

This was a few years ago. There was even a discussion thread on this list
that showed preference to make that change.

https://lists.gnu.org/archive/html/emacs-orgmode/2017-10/msg00449.html

Re: Parentheses in section titles interfere with on-screen font choice

[Richard Stanton]

Much dissection of init.el later, it seems the problem was caused by an 
interaction with (an outdated version of) another package, rainbow-delimiters. 
Updating this seems to solve the problem.

Best,

Richard

> On Apr 27, 2020, at 3:00 AM, Nicolas Goaziou  wrote:
> 
> Hello,
> 
> Richard Stanton mailto:rhstan...@berkeley.edu>> 
> writes:
> 
>> When using org mode (9.3.6), I’ve noticed that putting parentheses
>> into a section title seems to change the font used to display the
>> title on the screen. So, for example, on my machine
>> 
>> * Heading
>> 
>> displays in a red font.
>> 
>> If I add something in parentheses, e.g.,
>> 
>> * Heading (with parentheses)
>> 
>> the title now displays in grey. As I’m typing, the font change occurs the 
>> moment I type the first character after the open parenthesis.
>> 
>> The behavior is similar for lower level headers too. Is this
>> deliberate? And if so, is there a way to put parentheses into section
>> titles without interfering with the display font?
> 
> I cannot reproduce it. Is there something in your config?
> 
> Regards,
> 
> -- 
> Nicolas Goaziou

Re: Parentheses in section titles interfere with on-screen font choice

[Richard Stanton]

I’ll investigate further...

> On Apr 27, 2020, at 3:00 AM, Nicolas Goaziou  wrote:
> 
> Hello,
> 
> Richard Stanton mailto:rhstan...@berkeley.edu>> 
> writes:
> 
>> When using org mode (9.3.6), I’ve noticed that putting parentheses
>> into a section title seems to change the font used to display the
>> title on the screen. So, for example, on my machine
>> 
>> * Heading
>> 
>> displays in a red font.
>> 
>> If I add something in parentheses, e.g.,
>> 
>> * Heading (with parentheses)
>> 
>> the title now displays in grey. As I’m typing, the font change occurs the 
>> moment I type the first character after the open parenthesis.
>> 
>> The behavior is similar for lower level headers too. Is this
>> deliberate? And if so, is there a way to put parentheses into section
>> titles without interfering with the display font?
> 
> I cannot reproduce it. Is there something in your config?
> 
> Regards,
> 
> -- 
> Nicolas Goaziou

Re: Parentheses in section titles interfere with on-screen font choice

[Nicolas Goaziou]

Hello,

Richard Stanton  writes:

> When using org mode (9.3.6), I’ve noticed that putting parentheses
> into a section title seems to change the font used to display the
> title on the screen. So, for example, on my machine
>
> * Heading
>
> displays in a red font.
>
> If I add something in parentheses, e.g.,
>
> * Heading (with parentheses)
>
> the title now displays in grey. As I’m typing, the font change occurs the 
> moment I type the first character after the open parenthesis.
>
> The behavior is similar for lower level headers too. Is this
> deliberate? And if so, is there a way to put parentheses into section
> titles without interfering with the display font?

I cannot reproduce it. Is there something in your config?

Regards,

-- 
Nicolas Goaziou

Parentheses in section titles interfere with on-screen font choice

[Richard Stanton]

When using org mode (9.3.6), I’ve noticed that putting parentheses into a 
section title seems to change the font used to display the title on the screen. 
So, for example, on my machine

* Heading

displays in a red font.

If I add something in parentheses, e.g.,

* Heading (with parentheses)

the title now displays in grey. As I’m typing, the font change occurs the 
moment I type the first character after the open parenthesis.

The behavior is similar for lower level headers too. Is this deliberate? And if 
so, is there a way to put parentheses into section titles without interfering 
with the display font? 

Thanks.

Richard Stanton

Re: Why not org-tempo insert upcased strings?

[tsuucat]

> tsuucat  writes:
> 
>>> Yes, the convention is now to have downcased keywords. 
>> Thanks. Is the convention documented?
>> 
>> https://orgmode.org/manual/Structure-Templates.html#Structure-Templates 
>> 
>> It doesn’t seems that The Org Manual uses such a convention.
> 
> While the manual doesn't recommend which you should prefer (I don't
> think), it does provide a rationale for its use of uppercase:
> 
>(info "(org)Conventions")
>

Hmm…
According to etc/ORG-NEWS, org-tempo.el was introduced in Org 9.2.
Unfortunately the section doesn’t refer the change of convention.

Why the convention is changed in org-tempo?

--
tsuucat

Re: small patch for ox-bibtex.el in contrib

[Eric S Fraga]

On Friday, 24 Apr 2020 at 22:25, Nicolas Goaziou wrote:
> Thank you. I eventually pushed a different fix as I noticed other issues
> in the code. Could you confirm it still solves your problem?

Yes, thank you.  Jumping to an entry in my bibliography file works
perfectly. I've not tested anything else yet but will let you know if I
run into anything strange.

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-546-gb4e91b