On Tuesday, 4 May 2021 at 22:22, Nicolas Goaziou wrote:
> I meant: is it useful to even mention it? Is it used at all when other
> more complete solutions exist?
Actually, to avoid misunderstanding, natbib is not more "complete" than
the default LaTeX support. It simply supports a particular
On Tuesday, 4 May 2021 at 18:59, Nicolas Goaziou wrote:
> Is the default \cite{key} command (without any other package) used?
Yes, it is. But I wouldn't be able to tell you anything about relative
frequency etc.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.5-395-g82fbdd
Have been trying to execute multiple calc commands, but when I evaluate the calc
expressions, I get just one result.
This does not work
#+begin_src calc
fsolve(x*2+x=4,x)
fsolve([x + y = a, x - y = b],[x,y])
#+end_src
But this works
#+begin_src calc
fsolve(x*2+x=4,x)
Have been looking to find some examples on using orgbabel with fortran code
but have not found information.
Regards
P*
Sébastien Miquel writes:
Hi Bastien,
Bastien writes:
I tried to apply this (transitory?) patch against maint and it
did not
apply. It applies okay on master. For bug fixes, please make
patches
againt the maint branch.
This fixes a bug introduced by a commit in master. I've attached
the
Fr Ml writes:
> If the cursor is on a <> and the item has a CUSTOM_ID then a
> link to the headline (with the CUSTOM_ID) is stored - and not the link to the
> target.
> This behavior is not always the same.
Confirmed on master.
Recipe:
1. Create the following org file:
* test
:PROPERTIES:
Maxim Nikulin writes:
> helm-org-ql.el that is a part of org-ql does not use cache when calling
> org-get-outline-path. helm-org performs sequential scan similar to
> org-refile-get-targets.
Hmm. You are right. But they could. I myself ran into an issue with
helm-org-ql exactly because
Hi Bastien,
Bastien writes:
I tried to apply this (transitory?) patch against maint and it did not
apply. It applies okay on master. For bug fixes, please make patches
againt the maint branch.
This fixes a bug introduced by a commit in master. I've attached the same
patch here, properly
Hi Nick,
Nick Savage writes:
> I've attached a patch to address this.
Applied in maint, thanks a lot!
--
Bastien
I've attached a patch to address this.
The issue is that ob-sqlite.el uses org-babel-string-read, which
purposefully removes double-quotes. I think this is unintended
behaviour, and it only seems to be used with ob-sqlite.el. I added a
minor function to bypass the part of
Hi Sébastien,
Sébastien Miquel writes:
> I'll see if I can fix this bug and keep the security improvements. In
> the meantime, you can apply the attached patch that should fix
> your issue.
I tried to apply this (transitory?) patch against maint and it did not
apply. It applies okay on
No Wayman writes:
Subsequent tangles did not fail for me.
Ah yes, I understand, it is possible to delete a file without write
permission.
I'll see if I can fix this bug and keep the security improvements. In
the meantime, you can apply the attached patch that should fix
your issue.
Thank you
Hi,
"Steven Bagley" writes:
> Yes, that works for the example I quoted. The source of the original
> "::" is org-mac-link, not my typing. Maybe that could insert a
> different character sequence to avoid any confusion.
I had a look at org-mac-link.el but could not figure out what was
causing
"Bruce D'Arcus" writes:
> On Tue, May 4, 2021 at 12:59 PM Nicolas Goaziou
> wrote:
>> Is the default \cite{key} command (without any other package) used? I'm
>> not sure we should provide it since we are working towards more complete
>> solutions.
>
> Not ATM.
>
> The table only has suggested
On Tue, May 04 2021, Denis Maier wrote:
> Well, IIRC, in author-year styles \autocite is equivalent to \parencite. I
> think, what the manual talks about is not that \autocite wouldn't be
> appropriate
> for author-year styles, but rather that relying /solely/ on \autocite doesn't
> give
Hi Nicolas,
On Tue, May 04 2021, Nicolas Goaziou wrote:
> If you think my assumption is incorrect, please let me know what kind of
> hook would be required.
No, I don't think there's anything Org should provide. I just wanted to be sure
I hadn't missed anything.
>> - =:active= just means
Hi Jonas,
Jonas Bernoulli writes:
> All the *ELPAs extract metadata from the "main library", which by
> default is the library whose name matches the name of the package.
>
> If the name doesn't match, then it can be overridden, but some
> main library is required, even if it does nothing but
Sébastien Miquel writes:
Hi,
No Wayman writes:
I'm tangling my early-init/init.el with the :tangle-mode header
arg set to
(identity (#o444)).
This should be `(identity #o444)` I believe ?
Apologies, I transcribed that incorrectly. I do have `(identity
#o444)`.
File permissions are
Am 04.05.2021 um 17:27 schrieb Joost Kremers:
On Tue, May 04 2021, Bruce D'Arcus wrote:
On Tue, May 4, 2021 at 10:47 AM Joost Kremers wrote:
I can add some comments regarding biblatex:
- default: \parencite[1]
WDYT of \autocite for default?
It's conceptually the same as the CSL default.
Hi,
No Wayman writes:
I'm tangling my early-init/init.el with the :tangle-mode header arg
set to (identity (#o444)).
This should be `(identity #o444)` I believe ?
The idea behind this was to prevent myself from accidentally editing
the tangled source files
instead of the Org files.
Hello,
I have a problem with the function org-store-link it doesn't
work as
described in the documentation:
https://orgmode.org/manual/Handling-Links.html
"For Org files, if there is a '<>' at point,
the link points to
the
Dear All,
this is just to indicate that I've started to look into the
wip-cite-new branch with an eye on updating citeproc-org to use the
new API -- everything seems to be working perfectly, thanks again for
this, Nicholas! One issue I also noticed is the separation of citation
style and
Maxim Nikulin writes:
> On 04/05/2021 14:30, Aleksandar Dimitrov wrote:
>>
>> I don't usually switch input methods. Instead I rely on the X-Server's
>> facilities, including group toggles and XCompose. For example I use
>> XCompose to write all languages with a Latin alphabet without having to
Le 04 May 2021, Bastien a écrit :
>> I typically use it directly, but if the maintenance burden is
>> manageable, I could offer maintenance here, too (once I have the papers
>> in place).
>
> Thanks also for this then!
>
Thanks as well ! It’s good to know that knowledgeable people might care
I'm tangling my early-init/init.el with the :tangle-mode header
arg set to (identity (#o444)).
The idea behind this was to prevent myself from accidentally
editing the tangled source files
instead of the Org files. Unfortunately, since a3cb9b853 there
seems to be a behavior change for
On Tue, May 4, 2021 at 12:59 PM Nicolas Goaziou wrote:
> AFAIU, the idea is to use styles from you wiki. However, sub-styles are
> not mentioned. They could be "full" for the starred variants, "caps" for
> the capitalized ones, and "alt" for those without parenthesis, so one
> could write:
Bastien writes:
> The files previously stored in the contrib/ directory of Org's repo
> now lives here: https://git.sr.ht/~bzg/org-contrib
Congrats.
Better late than never. ;D
> The plan is to build a NonGNU ELPA package called "org-contrib",
> we will see if that's feasible.
All the *ELPAs
On Tue, May 4, 2021 at 12:59 PM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
...
> > I guess the question at this stage is how to iterate this.
> >
> > I already added a change or two based on feedback from Joost, and it
> > does make sense to add a new column for latex.
> >
> > It seems
On 04/05/2021 14:30, Aleksandar Dimitrov wrote:
I don't usually switch input methods. Instead I rely on the X-Server's
facilities, including group toggles and XCompose. For example I use
XCompose to write all languages with a Latin alphabet without having to
switch layouts/input methods.
You
On 02/05/2021 13:59, Ihor Radchenko wrote:
Maxim Nikulin writes:
Some additions. org-outline-path-cache is used solely by
org-refile-get-targets (maybe there are some calls in other packages)
but it efficiency is questionable. It was not clear for me earlier that
the cache is reset before each
"Bruce D'Arcus" writes:
> On Tue, May 4, 2021 at 11:46 AM Eric S Fraga wrote:
>
>> I wonder whether it might be good to have a default LaTeX column as
>> well, i.e. not natbib, a column that represents what LaTeX supports out
>> of the box which is only the \cite{key} command.
>
> Makes sense
Hello,
Joost Kremers writes:
> - A user should be able to insert citations into an Org document. IIUC nothing
> in org-cite provides any functionality for this, right? Is there a default
> list of styles a user would expect to be supported, or does this depend
> solely
> on the
On Tue, May 4, 2021 at 11:46 AM Eric S Fraga wrote:
> I wonder whether it might be good to have a default LaTeX column as
> well, i.e. not natbib, a column that represents what LaTeX supports out
> of the box which is only the \cite{key} command.
Makes sense to me.
I guess the question at this
On Tuesday, 4 May 2021 at 11:20, Bruce D'Arcus wrote:
> I'm attaching the tentative style/command and shortcut mapping I came
> up with, with help from Eric and Joost.
Thank you for this.
I wonder whether it might be good to have a default LaTeX column as
well, i.e. not natbib, a column that
On Tue, May 4, 2021 at 11:26 AM Joost Kremers wrote:
> In order to get ... parentheses around the locator, you need to use
> \pnotecite:
> ...
> \notecite gives the locator without parentheses.
Ah, right then.
I updated the wiki table with that.
This is an example where sub-styles could be
On Tue, May 04 2021, Bruce D'Arcus wrote:
> On Tue, May 4, 2021 at 10:47 AM Joost Kremers
> wrote:
>
>> I can add some comments regarding biblatex:
>>
>> - default: \parencite[1]
>
> WDYT of \autocite for default?
>
> It's conceptually the same as the CSL default.
If that is the case then
On Tue, May 04 2021, Bruce D'Arcus wrote:
> One other little thing:
>
> On Tue, May 4, 2021 at 10:47 AM Joost Kremers
> wrote:
>
>> - locators: \notecite[3]
>
> Are you sure about this?
Well, no, I hadn't tried it... I did mention there were variants, though. ;-)
> Here's the use case:
>
>
I'm attaching the tentative style/command and shortcut mapping I came
up with, with help from Eric and Joost.
HTH.
I do have \autocite as default for biblatex. Joost can weigh in if he
thinks this is a problem.
Bruce
org-cite-styles.org
Description: Binary data
One other little thing:
On Tue, May 4, 2021 at 10:47 AM Joost Kremers wrote:
> - locators: \notecite[3]
Are you sure about this?
Here's the use case:
https://github.com/jgm/pandoc/issues/7205
Bruce
On Tue, May 4, 2021 at 10:47 AM Joost Kremers wrote:
> I can add some comments regarding biblatex:
>
> - default: \parencite[1]
WDYT of \autocite for default?
It's conceptually the same as the CSL default.
> - text: \textcite
> - author: \citeauthor[2]
> - title: \citetitle[2]
> - year:
Hello,
While testing another patch for agenda fontification, I noticed that
agenda can spend up to half!! time doing org-up-heading-safe. Mostly
inside queries for inherited tags and properties.
I managed to make org-up-heading-safe up to 50x faster using position
cache.
If this patch also
Ihor Radchenko writes:
> Bastien writes:
>> Could it slow down agenda generation for some configurations?
> The total slowdown is ~30%, though the second part will only be slow
> before the headings are fontified first time by
> org-buffer-substring-fontified. Subsequent agenda rebuilds will
On Tue, May 04 2021, Bruce D'Arcus wrote:
> On Tue, May 4, 2021 at 9:27 AM Joost Kremers wrote:
>
>> - A user should be able to insert citations into an Org document. IIUC
>> nothing
>> in org-cite provides any functionality for this, right? Is there a default
>> list of styles a user
On Tue, May 4, 2021 at 9:27 AM Joost Kremers wrote:
> - A user should be able to insert citations into an Org document. IIUC nothing
> in org-cite provides any functionality for this, right? Is there a default
> list of styles a user would expect to be supported, or does this depend
>
Hello,
Nicolas Goaziou writes:
>> Should one want to convert LaTeX images say to an SVG for HTML export, I
>> do not think one would want this behaviour to also apply to LaTeX being
>> exported to markdown.
>
> Why do you think so? This is consistent with everything else not
> supported by
Sorry, just to be crytal clear ...
On Tue, May 4, 2021 at 9:21 AM Bruce D'Arcus wrote:
> > It is possible to include sub-styles, e.g.,
>
> I agree it would be better to allow variants ...
I should have written "sub-styles"; as in, I agree with Nicolas.
Also agree on shortcuts, which I've
Hi list,
As the maintainer of Ebib, I have of course been following the threads on
citation support for Org with some interest. I have not been able to follow
every detail, however, in part probably due to my limited experience with CSL
and citeproc. (I use biblatex myself.)
Now I find myself
On Tue, May 4, 2021 at 9:15 AM Nicolas Goaziou wrote:
> Also, what styles (including shortcuts if necessary) names could we
> chose? Asterisk is not allowed in the citation style (but that could
> change, if necessary).
I'll let the bibtex folks speak to that perspective, but ...
> E.g.,
>
>
Eric S Fraga writes:
> On Tuesday, 4 May 2021 at 07:58, Bruce D'Arcus wrote:
>> Perhaps the bibtex/biblatex folks can help with those details?
>
> For natbib, there is a good summary at
>
> http://merkel.texture.rocks/Latex/natbib.php
Thanks.
Naive question: it doesn't say how to print the
Hello,
Timothy writes:
> Should one want to convert LaTeX images say to an SVG for HTML export, I
> do not think one would want this behaviour to also apply to LaTeX being
> exported to markdown.
Why do you think so? This is consistent with everything else not
supported by vanilla Markdown.
>
On Tuesday, 4 May 2021 at 07:58, Bruce D'Arcus wrote:
> Perhaps the bibtex/biblatex folks can help with those details?
For natbib, there is a good summary at
http://merkel.texture.rocks/Latex/natbib.php
I only ever typically use "Author (year)" (\citet{key}) and "(Author,
year)" (\citep{key})
On Tuesday, 4 May 2021 at 06:11, Bruce D'Arcus wrote:
> It should be trivial to map this to latex; cite/text -> \citet and such.
Indeed.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.5-395-g82fbdd
On Tuesday, 4 May 2021 at 12:10, Joost Kremers wrote:
> Pedantic nit-pick: they *should* be expecting and using biblatex. (But
> perhaps that is what you meant already. :-) )
Well, luckily, in my field most of the journals allow submissions in
LaTeX and provide style files. The bibliography is
On Tue, May 4, 2021 at 6:48 AM Bruce D'Arcus wrote:
> It seems like those interested in this could collaborate on a table of
> style/command mappings for the above export processors.
>
> Anyone interested in working on this?
>
> If yes, how/where?
I added a wiki page on the bibtex-actions site
Hi,
I must confess I haven't followed all the nooks and crannies of this subject,
but when I browsed through the latest batch of contributions, I noticed that
one simple (=crude) workaround hasn't been mentioned; Indirect buffers.
If one uses one indirect buffer per language, it should be
Hi Victor,
"Victor A. Stoichita" writes:
> Le 03 May 2021, Bastien a écrit :
>> I suggest a criterium for keeping ob*.el files in Org could be that
>> the extension is known by Emacs _or_ that the supported language is
>> well-established.
>
> I happen to be an active user of ob-lilypond.
Hi,
"Dr. Arne Babenhauserheide" writes:
> Lilypond is not just well-established, it is the dominant tool for note
> engraving. One of the few domains in which no proprietary comes close in
> terms of quality.
>
> I typically use it directly, but if the maintenance burden is
> manageable, I
Hi,
"Dr. Arne Babenhauserheide" writes:
> This is well-established, and once I have my paperwork in place I would
> offer maintenance, because this is a major part of the lectures I write
> in org-mode.
Thanks for volunteering here. Let me know when the paperwork is done
so that I can you as
On Tue, May 4, 2021 at 2:47 AM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
> > And if the processor is citeproc-org, where does one put the "foo.csl"
> > style?
>
> That may be orthogonal. If you use a given "foo.csl", does it still make
> sense to provide styles to print_bibliography
On Tue, May 4, 2021 at 6:29 AM Nicolas Goaziou wrote:
> The branch provides an API to develop citation processors. The goal is
> not to ultimately use "oc-basic.el", but to activate more specialized
> processors, like, for example "oc-citeproc.el", but also
> "oc-biblatex.el" or "oc-natbib.el",
Ihor Radchenko writes:
> Arthur Miller writes:
>> ... Example can be seen in attached screenshot from
>> my init file where I use org headings to form a list of packages to
>> install, and checkboxes to indicate if a package configuration is used
>> or not.
>
> Depending on details of your
Bastien writes:
> Less code is less bug and less maintainance. So I'm considering
> moving these files to the new (unmaintained) org-contrib repo at
> https://git.sr.ht/~bzg/org-contrib:
>
> - ob-ditaa.el --- Babel Functions for ditaa
This is well-established, and once I have my paperwork in
Am 04.05.2021 um 12:10 schrieb Joost Kremers:
On Tue, May 04 2021, Eric S Fraga wrote:
Question for the longer term: for LaTeX export, I will be wanting to
have the [cite:] constructs export to BiBTeX code. Will this be
possible in due course? For other targets (ODT, HTML), what has been
Victor A. Stoichita writes:
> Le 03 May 2021, Bastien a écrit :
>> I suggest a criterium for keeping ob*.el files in Org could be that
>> the extension is known by Emacs _or_ that the supported language is
>> well-established.
>
> I happen to be an active user of ob-lilypond. Lilypond is
Hello,
Eric S Fraga writes:
> Question for the longer term: for LaTeX export, I will be wanting to
> have the [cite:] constructs export to BiBTeX code. Will this be
> possible in due course? For other targets (ODT, HTML), what has been
> done in this branch is fantastic but, for LaTeX,
On Tue, May 4, 2021, 5:51 AM Eric S Fraga wrote:
> On Tuesday, 4 May 2021 at 11:33, Nicolas Goaziou wrote:
> > Done.
>
> Thank you. Seems to work just fine.
>
> Question for the longer term: for LaTeX export, I will be wanting to
> have the [cite:] constructs export to BiBTeX code. Will this
On Tue, May 04 2021, Eric S Fraga wrote:
> Question for the longer term: for LaTeX export, I will be wanting to
> have the [cite:] constructs export to BiBTeX code. Will this be
> possible in due course? For other targets (ODT, HTML), what has been
> done in this branch is fantastic but, for
On Tuesday, 4 May 2021 at 11:33, Nicolas Goaziou wrote:
> Done.
Thank you. Seems to work just fine.
Question for the longer term: for LaTeX export, I will be wanting to
have the [cite:] constructs export to BiBTeX code. Will this be
possible in due course? For other targets (ODT, HTML), what
On Tuesday, 4 May 2021 at 10:29, Joost Kremers wrote:
> It's not really an input method, more like the lack of one. You're probably
> using =set-input-method= to change input methods? Check out
> =toggle-input-method=. :-)
Ah, interesting. A lack of input method. Kind of non-obvious. But the
Nicolas Goaziou writes:
> Oops. I'll fix it in a few hours. I need to treat LaTeX-derived
> back-ends specially in the context of BibTeX files.
>
> I'll let you know when it's done.
Done.
Hi Juan,
> Thank you very much for your interesting comments. I think your idea of
> applying org-babel to (multi) language support is tremendously
> suggestive and, of course, more org-centric. I suppose it could be
> applied also to languages within the paragraph by inline blocks... I
> really
On Tue, May 04 2021, Eric S Fraga wrote:
> So, on this note, without hopefully hijacking the thread, maybe somebody
> can tell me: what is the "default" input method, i.e. the one I get when
> I start Emacs and haven't changed input methods at all? I see no way to
> get back to it once I have
On Monday, 3 May 2021 at 20:47, Greg Minshall wrote:
> but, for me (maybe i'm missing something?) it means i switch input
> methods.
Which is what I do.
So, on this note, without hopefully hijacking the thread, maybe somebody
can tell me: what is the "default" input method, i.e. the one I get
> I like Aleksandar's solution quite a bit because it also works inline
> e.g. as src_org[:lang de]{Meine deutsch ist zher schlect!}. In
> principle this means that you could leverage the org-babel and org-src
> buffer system to get flyspell results in that language in line as well
> (though I
Hi Joost
> [Not directly related to the OP, but might be useful to know.]
>
> On Mon, May 03 2021, Aleksandar Dimitrov wrote:
>> this sounds very interesting to me, as I, too, mostly write in Org
>> and, sometimes write documents in multiple languages, usually with
>> different varieties of
On Tuesday, 4 May 2021 at 01:49, Timothy wrote:
> For the future, I'd think Julia actually warrants 1st class inclusion in
> Org, and I've instigated an effort to write an ob-julia that works well.
+1! Happy to help test if you wish. I use Julia as my programming
language these days.
--
:
On Monday, 3 May 2021 at 09:58, Bruce D'Arcus wrote:
>> 2. the suppressed author case does not seem to work.
>
> He removed the suppress author variant on the individual cited items,
> so I think the same effect he means to achieve with the "year" style.
Makes sense. Thank you.
--
: Eric S
On Monday, 3 May 2021 at 18:48, Nicolas Goaziou wrote:
> I don't know how to do that cleanly. However, I think this is already
> too smart a feature for "basic" back-end. So, I'd like to punt on this
> one.
Point taken. Reasonable approach. Thank you.
--
: Eric S Fraga via Emacs 28.0.50, Org
Hi Greg,
>> Apart from the export, one of my biggest gripes is
>> flyspell. Specifically, the fact that you have to choose one language to
>> spell check the entire document with. That is insufficient in my case.
>
> in case it's relevant:
>
> i also switch between languages. but, for me (maybe
Hi,
Am 04.05.2021 um 08:47 schrieb Nicolas Goaziou:
Hello,
"Bruce D'Arcus" writes:
On Mon, May 3, 2021 at 12:42 PM Nicolas Goaziou wrote:
Anyway, I suggest to let it nil, and select it at the document level
instead, with
#+cite_export: basic bibstyle citestyle
What is the
Hello,
"Bruce D'Arcus" writes:
> On Mon, May 3, 2021 at 12:42 PM Nicolas Goaziou
> wrote:
>
>> Anyway, I suggest to let it nil, and select it at the document level
>> instead, with
>>
>> #+cite_export: basic bibstyle citestyle
>
> What is the significance of the last two items?
These are
Hi Gustavo,
Gustavo Barros writes:
> some time ago, I've reported an issue regarding duplicity of the default
> candidate in `org-refile'
> (https://orgmode.org/list/87lftw1k2n@gmail.com/). The problem was
> that, when using `org-refile-use-outline-path' an "extra" slash was
> appended
82 matches
Mail list logo
