András Simonyi writes:
> the attached patch adds support for filter-based sub-bibliographies in the
> "csl"
> org-cite export processor. It supports the same syntax for specifying
> filters as the biblatex processor and supports some of the biblatex
> filter types, concretely, entry-type and key
Sébastien Miquel writes:
> Ihor Radchenko writes:
>> Can you provide more concrete examples?
>>
>>> Some drawbacks:
>>> + doesn't work for all languages (does work for LaTeX)
>> Which languages do not work?
> Most languages do not work. Using your proposed solution, what I'm
> trying to do is
Hugo Heagren writes:
>> Currently, the internal implementation will treat nil return value as if
>> there was no :default-description and org-link-make-description-function
>> were set to nil. We may probably document this. It sounds like a useful
>> behavior.
>
> I added some relevant documentat
Christian Heinrich writes:
> I looked at the code and came up with a patch that works for me (see below).
> However, this may
> change behavior for others:
Thanks!
> 1. The original %^g will work on non-headlines, but if (org-set-tags-command)
> is called as I do,
> this is no longer possible
Daniel Ortmann writes:
> More information on that character:
>
> position: 195 of 690 (28%), column: 26
> character: ⭠ (displayed as ⭠) (codepoint 11104, #o25540,
> #x2b60)
> charset: unicode-bmp (Unicode Basic Multilingual Plane
> (U+..U+))
> c
Henrik Frisk writes:
>>> Is so, you probably need
>>>
>>> org-protocol://capture?template...
>>> instead of
>>> org-protocol://capture-html?template...
>>>
>>> Thanks, that was the issue and it works fine now. However, I can't seem
>> to get the org-capture-ref-get-bibtex-field to work by simply
Bhavin Gandhi writes:
> Seems like soon I will cross the TINYCHANGE limit, so I will get the
> FSF copyright assignment done.
Note that FSF should reply within 5 working days. If not, we can help
you to push them.
Best,
Ihor
Hi Max,
I’ve just made a few more tweaks, tested it, and pushed this as 0583a0c. We may
want to tweak this further before the next Org release, but I think this is a
good enough starting point.
> An idea: a menu entry that displays location in the org file that caused the
> prompt. However it may
Daniele Pizzolli writes:
> From 897ae50cf055d459d741c90f8de94dd56a8eb3d9 Mon Sep 17 00:00:00 2001
> From: Daniele Pizzolli
> Date: Wed, 5 May 2021 17:00:28 +0200
> Subject: [PATCH 1/1] Add disabled test for % in babel shell output
Daniele, your patch is over 15LOC. Would you mind doing FSF pape
Ihor,
> The current behaviour of :var foo=name-of-src-block is assigning result
> of evaluation. However, this behaviour is actually not documented.
> 16.4 Environment of a Code Block section of the manual only documents
> uses like
in fact, the text of the info page (on my system?) says
> code b
Greg Minshall writes:
>> The current behaviour of :var foo=name-of-src-block is assigning result
>> of evaluation. However, this behaviour is actually not documented.
>> 16.4 Environment of a Code Block section of the manual only documents
>> uses like
>
> in fact, the text of the info page (on m
Ihor,
> Alternative ideas are welcome though. I'd prefer to avoid breaking
> change if we can find an equally simple syntax alternative to assign
> source block code to a variable.
my two cents would be to avoid the breaking change. (i notice, for
example, that i use this construct in some of my
Hi all,
I am writing a package for LuaLaTeX and have decided to use Org for it.
The reasons: org is more powerful, more versatile and more cool than the
'official' LaTeX literate programming utility, docstrip.
Searching for information on this list I found this post from Marcin
Borkowski, from 20
Hi Ihor,
thanks for your feedback. I attached a patch, but I'm not sure why you said
"all but the last line".
That last line for me was (org-set-tags tags), which proved important as
otherwise the tags were not
set in the buffer.
Anyways, please find the patch attached. Feedback is welcome, par
Hi there!
When I add a timestamp through, for instance, scheduling (C-c s), the
day abbreviation is translated to my local language, that is, Spanish.
However all calendar variables, calendar-*, and, more specifically,
calendar-day-{name,header,abbrev}-array have not been modified and
keep their d
And it does highly complex context matching for many common patterns out of the
box with no need for customization.
— rsw
> On Jul 7, 2022, at 8:26 AM, Ihor Radchenko wrote:
>
> Max Brieiev writes:
>
>> Embark defines the following targets: file, symbol, URL, s-expression,
>> defun, etc. It
Just noting that we have seen this and will have a look.
-- rsw
> On Jul 16, 2022, at 7:16 PM, Robert Weiner wrote:
>
> And it does highly complex context matching for many common patterns out of
> the box with no need for customization.
>
> — rsw
>
>> On Jul 7, 2022, at 8:26 AM, Ihor Radch
Cédric Martínez Campos writes:
> Hi there!
>
> When I add a timestamp through, for instance, scheduling (C-c s), the
> day abbreviation is translated to my local language, that is, Spanish.
> However all calendar variables, calendar-*, and, more specifically,
> calendar-day-{name,header,abbrev}
Hi,
Ihor, Hugo raised a question how to interpret nil returned by
:insert-description functions. Do you have any opinion? I do not like
the idea to consider it as an error since string is expected. I would
prefer to call `org-link-make-description-function' as a fallback.
On 17/07/2022 04:20
19 matches
Mail list logo
