On 26/07/2022 11:26, K K wrote:
On 2022-07-26 Tue. 09:23 +0700，Max Nikulin wrote：
> However the suggestion was namely to use U+200B ZERO WIDTH SPACE and
> it
> is actually implemented since `org-emphasis-regexp-components'
> currently
> contains [:space:].
> ...
> K, could you, please, clarify
"Printing a bibliography" would also work.
--
: Eric S Fraga, with org release_9.5.4-648-gdf1814 in Emacs 29.0.50
Joseph Turner writes:
>> The solution will be simply removing the default :results setting.
>
> I think you're suggesting something like this:
>
> (defvar org-babel-default-header-args:plantuml
> '((:exports . "results"))
> "Default arguments for evaluating a plantuml source block.")
>
> With
András Simonyi writes:
>> See the attached.
>
> Thanks a lot for the improvements! The only suggested change which I'm
> not sure about is the renaming of the section "Bibliography printing"
> to "Printing bibliography" Neither of them are ideal but it's
> difficult to find a formulation which so
Juan Manuel Macías writes:
> Ihor Radchenko writes:
>
>>> -(org-back-to-heading t) ; Sets match data
>>> -(match-end 0))
>>> +(re-search-backward org-heading-regexp) ; Sets match
>>> data
>>> +(match-beginning 0))
>>
On 2022-07-26 Tue. 09:23 +0700，Max Nikulin wrote：
> However the suggestion was namely to use U+200B ZERO WIDTH SPACE and
> it
> is actually implemented since `org-emphasis-regexp-components'
> currently
> contains [:space:].
> ...
> K, could you, please, clarify what is your particular use case?
hi, Munyoki,
i'm neutral w.r.t. asymptote support being in "core org" or in
"contrib". but, ...
> I'm not _against_ supporting a proffesional-level
> graphics PL. What I'm trying to say is that
> having it installed should be a choice made by the
> end-user. Personally, I try to keep my system
On 26/07/2022 08:26, Ihor Radchenko wrote:
K writes:
The thread and post I am mentioning is at
https://list.orgmode.org/orgmode/87bodxy77m@bzg.ath.cx/
That thread references yet another thread at
http://thread.gmane.org/gmane.emacs.orgmode/59881/focus=59971
However, gname links are no lon
Jarmo Hurri writes:
>> TBH, this is the first time I'm hearing about it. I've looked it up,
>> and indeed it seems to be useful.
>
> For some reason, even people who would certainly benefit from Asymptote
> often have not heard of it. The developers do not really
> advertise. Asymptote is amaz
Jarmo Hurri writes:
>> Then, would it make more sense to include ob-asymptote.el into the
>> asymptote distribution?
>
> I do not think this is a good idea:
>
> - I am not involved in the development of asymptote, so this solution
> would put maintenance of ob-asymptote.el beyond my reach.
AFA
K writes:
> The thread and post I am mentioning is at
> https://list.orgmode.org/orgmode/87bodxy77m@bzg.ath.cx/
That thread references yet another thread at
http://thread.gmane.org/gmane.emacs.orgmode/59881/focus=59971
However, gname links are no longer working.
Do you happen to know which t
Hello everyone, I am a chinese user and also came across this problem.
Bastin once wrote this almost a decade ago:
> More precisely this can be included when we decide to drop support
> of Emacs 22.
>
> Does anyone know what is the current backward compatibility state
> of major native Emacs
Thank you for your feedback, Ihor!
> Most importantly, the patch does not change the default value of
> org-babel-default-header-args:plantuml. :results header arg is set to
> "file" by default.
Yes, I noticed this issue also.
> The solution will be simply removing the default :results setting.
Jarmo Hurri anaandika:
> Greetings Munyoki.
>
Hi!
[...]
>> That said, shouldn't this be in org-contrib? Too many features in a
>> tool - featurism - may be distracting, in the sense that you focus
>> more on your tool than work at hand.
>
> I do not understand this. Why would supporting a
Jarmo Hurri anaandika:
> Greetings Munyoki.
>
Hi!
[...]
>> That said, shouldn't this be in org-contrib? Too many features in a
>> tool - featurism - may be distracting, in the sense that you focus
>> more on your tool than work at hand.
>
> I do not understand this. Why would supporting a
On 7/25/22 01:50, Ihor Radchenko wrote:
The conventions sound reasonable, though I do not think that they are
documented in D.6 Tips for Documentation Strings section of the Elisp
manual.
Thanks, I added the following to the Elisp manual to try to fix that:
https://git.savannah.gnu.org/cgit/e
> Bastin once wrote this almost a decade ago:
Sorry for the misspelling, the name is Bastien, not Bastin.
The thread and post I am mentioning is at
https://list.orgmode.org/orgmode/87bodxy77m@bzg.ath.cx/
On Mon, Jul 25, 2022 at 2:26 PM András Simonyi wrote:
>
> Dear All,
>
> On Sun, 24 Jul 2022 at 09:41, Ihor Radchenko wrote:
> >
> > Thanks!
> >
> > I have made some changes to the patch, mostly fixing grammar issues (the
> > ones I can notice). I also changed the sub-section from "Bibliography
>
Hello everyone, I am a chinese user and also came across this problem.
Bastin once wrote this almost a decade ago:
> More precisely this can be included when we decide to drop support
> of Emacs 22.
>
> Does anyone know what is the current backward compatibility state
> of major native Emacs
Dear All,
On Sun, 24 Jul 2022 at 09:41, Ihor Radchenko wrote:
>
> Thanks!
>
> I have made some changes to the patch, mostly fixing grammar issues (the
> ones I can notice). I also changed the sub-section from "Bibliography
> options" to "Bibliography options in "biblatex" and "csl" export process
Hi, Ihor,
Here is a new fixed version of the patch, with the addition to NEWS.
Ihor Radchenko writes:
>> - (org-back-to-heading t) ; Sets match data
>> - (match-end 0))
>> + (re-search-backward org-heading-regexp) ; Sets match
>> data
Perry Smith writes:
> The text has “For example, to specify a date December 12, 2005 …” and then
> all of the examples use 12 and 1 as if the intention was “to specify a date
> December 1, 2005”. I doubt if you want to use December 12 because the
> specification would be 12 12 2005 but it wou
Juan Manuel Macías writes:
>> Clearly, the "possible after an ASCII export" dropped somewhere in the
>> middle.
>
> New version of the patch attached.
>
> `:comments org' now produces by default plain text comments previously
> exported to ascii from org.
Thanks!
This change should be in ORG-NEW
Ihor Radchenko writes:
> Morgan Smith writes:
>
>> I'm using emacs from commit f258f67 (quite recent) and org from commit
>> 39005dc (quite recent).
>>
>> I'm using native compilation and PGTK.
>
>> Debugger entered--Lisp error: (invalid-function org-encode-time)
>> org-encode-time((0 0 0 21 7
Joseph Turner writes:
> Allow src block execution without ":file" header arg. When ":file" is
> omitted, insert txt output in buffer below src block.
>
> TINYCHANGE
Thanks for your contribution!
This addition makes a lot of sense.
Some comments:
Most importantly, the patch does not change the
Ihor Radchenko writes:
> LaTeX is just one export backend to worry about. From broader
> perspective, we can have a generic template library.
Nice idea, I agree. I was targeting LaTeX specifically because of the
questions that have been raised in this thread and other parallel threads.
And becaus
Juan Manuel Macías writes:
> I agree that adding more elements to the standard preamble is a complex
> matter. LaTeX is already horribly complex and multiple, and it is
> difficult to satisfy all kinds of users with a standard code. It
> occurred to me that an alternative to modifying Org's code
Paul Eggert writes:
> The Emacs doc string convention is to document values as-is when that
> is clear, and surrounded by `single quotes' otherwise. For example, a
> doc string "(a b c)" stands for a list of symbols, and the doc string
> "`a'" stands for a single symbol. The doc string "\\=`a" is
28 matches
Mail list logo
