Hi Ihor,
thank you for your review.
Ihor Radchenko writes:
> According to our records in https://orgmode.org/worg/contributors.html,
> you haven't signed FSF copyright agreement. May you add a TINYCHANGE
> cookie to the commit message as required by
>
Looks to me like this only happens if the last word of the line is
"emphasized" and larger font.
I'm using emacs 28, org 9.5.5
#+OPTIONS: author:nil
#+OPTIONS: toc:nil
#+OPTIONS: date:nil
#+OPTIONS: ^:nil
#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
Hi,
Ihor Radchenko writes:
What I have in mind is an ability to parametrize the transcoders like
the following:
(org-export-define-backend 'html
'((paragraph . ((paragraph-is-a-link? figure-transcoder :name figure)
(:unless 'figure paragraph-transcoder
"Bruce D'Arcus" writes:
> I'm not really following this discussion, but is this perhaps similar
> to pandoc/djot's notion of "filters"?
>
> https://github.com/jgm/djot.js#filters
Nope. Filters are org-export-filters-alist.
What we are talking about is a generic way to test Org buffer contents
On 23 Feb 2023, Max Nikulin wrote:
On 23/02/2023 00:01, Karl Fogel wrote:
(when (not (keymap-lookup nil "C-"))
(keymap-local-set "C-" 'org-fold-hide-subtree))
So FWIW C- is not bound in Org Mode buffers for me, in
Emacs
30.x (i.e., recent development builds).
lisp/tab-bar.el:130:
No Wayman writes:
> It appears context is king.
> All that aside, I think Ihor's proposal sidesteps the whole issue
> while addressing the complexity of the implementation.
I read
#+cite_export: processor_x options:blablabla
as
"When I want to export citations using 'processor_x' , add options
Hi all,
the topic says it all. Is it possible? If so, how?
TIA,
--
Marcin Borkowski
http://mbork.pl
Timothy writes:
I hadn’t thought of applying the term “enrichment”. That or
adaptation could be
a good fit. I think I like the sound of “enriching the export”,
and I could
probably also be sold on “export adaptation” / “adaptive
export”.
Both are horribly abstract in my opinion.
If the
Ihor Radchenko writes:
I am looking at the concept again, and I feel that we may be
missing
some flexibility here. I do not like the fact that each feature
can only
have a simple implementation within specific backend.
Agreed
What I have in mind is an ability to parametrize the
On Wed, Feb 22, 2023 at 7:23 AM Ihor Radchenko wrote:
>
> Timothy writes:
>
> > Here is a list of terms which I’d feel comfortable applying to the system:
> > ⁃ export features
> > ⁃ export capabilities
> > ⁃ export snippets
>
> I am looking at the concept again, and I feel that we may be
And to add:
https://books.google.com/ngrams/graph?content=adaption%2Cadaptation%2Ccontext%2Cenhancement%2Cenrichment%2Cfeature_start=1800_end=2019=en-2019=3
It appears context is king.
All that aside, I think Ihor's proposal sidesteps the whole issue
while addressing the complexity of the
⁃ Providing capabilities via snippets can be framed as akin to
dynamically
gaining a feature.
I understand some snippets may be used to, for example, include a
latex package.
However, it's not a requirement that a snippet "add a
feature/capability" to a document.
What that snippet does
Soory for the re-post... Just setting up a new email client
On Sun, 5 Feb 2023 00:14:59 +0100 (CET) Edgar wrote:
> Dear Ihor,
> On Feb 4, 2023 at 12:31 PM, Ihor Radchenko wrote:Edgar
> Lux writes:
>> For example, ... the proposed idea is
>> a bit awkward:
>>
>> ...
>> #+cite_export:
I reinstalled org and this solved both (related) problems.
Thank you and apologies for not having sent the proper debugged error.
A.
El jue, 23 feb 2023 a las 11:42, Ihor Radchenko ()
escribió:
> Alexei Gilev writes:
>
> > Basically that: from yesterday, every time I kill Emacs, i get this
>
Rafael Laboissière writes:
> The following content is not displaying correctly for me (see attached
> screenshot):
>
>[[https://host/some/-/path][[pre link]]] this is underlined, but
> shouldn't be [[https://host/another/-/path][[post link]]]
>[[https://host/some/path][[pre link]]]
Dear Org Mode developpers,
The following content is not displaying correctly for me (see attached
screenshot):
[[https://host/some/-/path][[pre link]]] this is underlined, but shouldn't
be [[https://host/another/-/path][[post link]]]
[[https://host/some/path][[pre link]]] this is okay
Pedro Andres Aranda Gutierrez writes:
> Joining the discussion I seem to have missed before (because I was
> using a less org-ish solution).
Could you please reply in the linked thread? Otherwise, other
participants of that thread will not see your idea.
--
Ihor Radchenko // yantar92,
Org
Alexei Gilev writes:
> Basically that: from yesterday, every time I kill Emacs, i get this message.
> I never got this message before and I am not sure whether I should be
> saving or not.
This is related to another error you are experiencing.
Fixed, on main.
Alexei Gilev writes:
> Thanks for your time.
>
> When I try, however, to use functions like
> org-icalendar-combine-agenda-files or org-icalendar-export-to-ics, I get
> this error:
It would help if you provided a backtrace or, better, a reproducer
starting from Emacs -Q.
See
Bhavin Gandhi writes:
> These are init files specific to other packages installed via OS package
> manager. But those are not loaded, it seems in the above steps. I tried to
> run (featurep 'clang-format) and it returned nil, while this returns t
> in my normal Emacs instance.
> ...
> None of
赵一宇 writes:
> Here is an example, in org file
>
>
> #+name: test
> #+begin_src emacs-lisp :var a :results silent
> a
> #+end_src
>
>
> Now, if I execute
> (org-sbe "test" (a "123°34'23.34\"otherthing"))
> it would say: Reference 123°34'23.34"otherthing not found
Fixed, on main.
I made org-sbe
21 matches
Mail list logo
