Hi Ihor,
I had some trouble testing your patches, and the outcome is still unclear to
me: apparently (again, cannot be sure this is not caused by "improper"
application of the patches) the new version of org-persist, with default value
for o-p-remote-files (100), removes any remote file from the p
Lele Gaifax writes:
> Hi Ihor,
>
> I had some trouble testing your patches, and the outcome is still unclear to
> me: apparently (again, cannot be sure this is not caused by "improper"
> application of the patches) the new version of org-persist, with default value
> for o-p-remote-files (100),
Ulrich Mueller writes:
>> On Mon, 20 Dec 2021, Marco Wahl wrote:
>
>> Possibly a split of function org-make-manuals in org-make-manual and
>> org-make-guide and further create two single targets instead of the
>> current double target is more clear.
>
>> See the patch.
>
>> WDYT?
>
> Sure, th
On 21/12/2021 04:39, Marco Wahl wrote:
Possibly a split of function org-make-manuals in org-make-manual and
org-make-guide and further create two single targets instead of the
current double target is more clear.
Marco, have you considered the following idea (I have not tested it)?
org.texi o
Hi Max!
Max Nikulin writes:
> On 21/12/2021 04:39, Marco Wahl wrote:
>> Possibly a split of function org-make-manuals in org-make-manual and
>> org-make-guide and further create two single targets instead of the
>> current double target is more clear.
>
> Marco, have you considered the following
Inside org-babel code blocks, emacs matches parens incorrectly whenever
different bracket types (eg <> {} []) are used.
For example the following in an .org file will cause check-parens to throw
an error:
#+BEGIN_SRC emacs-lisp
(> 1 0)
#+END_SRC
Where in an .el it will interpret the parens c
Hello,
Here is my problem. The code below, that is the code of the page called
"index.php" works.
< https://www.vidal-rosset.net/fCube/ >
But I would be happy to have this prover in this web page
<
https://www.vidal-rosset.net/fcube_an_efficient_prover_for_intuitionistic_propositional_logic.htm
On 21/12/2021 19:48, Marco Wahl wrote:
From my point of view using singuar targets for org.texi and
orgguide.texi is the clearest path to go.
It matter of taste. I do not like code duplication.
I already committed a fix along these lines. (Hopefully it's okay.)
Thank you for the fix.
P
Dear all,
this configuration does not work.
#+begin_src emacs-lisp
(use-package ox-context
:straight (ox-context :type git :host github :repo
"Jason-S-Ross/ox-context")
:config
(add-to-list 'org-context-presets-alist
'("book" .
(:literal "\n\\environment juh.env-g
On 12/21/21 7:50 AM, juh wrote:
Dear all,
this configuration does not work.
#+begin_src emacs-lisp
(use-package ox-context
:straight (ox-context :type git :host github :repo
"Jason-S-Ross/ox-context")
:config
(add-to-list 'org-context-presets-alist
'("book" .
On 21.12.21 17:19, Jason Ross wrote:
Your configuration looks correct to me.
Can you verify that the lines
\environment juh.env-garamond
\environment juh.env-garamond-trimsize5-8
\environment juh.env-makeups
\environment juh.env-umbruch
\environment juh.env-heading
On 12/21/21 9:55 AM, juh wrote:
Yes:
%===
% Preset Commands
%===
\environment juh.env-garamond
\environment juh.env-garamond-trimsize
I think this is a known problem (Org probably needs a PROBLEMS or
KNOWN_PROBLEMS file in addition to a NEWS file).
Problem is that org treats things like <> as special paren syntax
because they are used by org. Unfortunately, this causes problems with
things like paren matching in org files if y
On 21.12.21 19:04, Jason Ross wrote:
There is a problem on the ConTeXt side of things. ox-context just calls
the ConTeXt process on the output file (it's exactly equivalent to
calling `context test.mkiv` from the terminal)
Very strange. I have to dig deeper.
Thanks!
juh
Am Dienstag, dem 21.12.2021 um 19:36 +0100 schrieb juh
Ok, one thing solved.
I normally call context with --mode=trimsize to activate the given
trimsize. Can I set this in org-mode?
When I manually compile test.mkiv I get the right page dimensions but
the layout is scrambled. Maybe interference
On 12/21/21 10:56 AM, juh wrote:
Am Dienstag, dem 21.12.2021 um 19:36 +0100 schrieb juh
Ok, one thing solved.
I normally call context with --mode=trimsize to activate the given
trimsize. Can I set this in org-mode?
When I manually compile test.mkiv I get the right page dimensions but
the la
Hi,
Daniel Fleischer writes:
> Hi, I want to add custom keywords to be highlighted. I used
> (font-lock-add-keywords nil '(("books" . org-level-4)) t)
>
> but nothing happens after I restart orgmode or call 'font-lock-update'.
The following works for me, in an org mode buffer:
,
| (f
Sup, y'all
I started using guile with Org Babel and I was a little confused that errors
weren't being reported. The attached patch will report the error the same way
as python evaluation does.
Actually, most of the code was taken from ob-python.el
Let me know if I'm missing anything so this ca
I have:
(setq org-hide-emphasis-markers t)
…and the following does not render right. In the first line I see the ‘_’
characters around “underline”, and it doesn’t underline the text.
In the second line, it works correctly. Apparently it needs some intervening
text (“foo” in this case).
The fi
Max Nikulin writes:
> On 21/12/2021 19:48, Marco Wahl wrote:
>>
>> From my point of view using singuar targets for org.texi and
>> orgguide.texi is the clearest path to go.
>
> It matter of taste. I do not like code duplication.
>
>> I already committed a fix along these lines. (Hopefully it's
Definitely a known issue. No easy way to fix it without someone doing
a deep pass on syntax propertization I think. I have a version of
rainbow delimiters mode that tries to work around this at least for
font locking, but it is severely broken and has some nasty quadratic
performance issues in larg
Hi,
I'm writing an exporter and I'd like to get :file property on a src block.
Let's say I have the following src block in an org file.
#+BEGIN_SRC ditaa :file images/hello-world.png :exports code
+--+
| Hello World! |
+--+
#+END_SRC"
And, say, I'm writing a function for
Ihor Radchenko writes:
> Though I am not a big fan of introducing yet another customisation.
> Maybe someone has better ideas?
I struggle to understand. Why do we need a customization? If Org knows
that some backend exists but has no execute function, why does it even
try to execute it? It ca
Felipe Lema writes:
> Sup, y'all
>
> I started using guile with Org Babel […]
Sup! I plan to write some literate Scheme soon as well. How do you find
the experience so far? As of today, I use 'scheme-mode' with a set of
TAGS files for completion and help, all based on my (incomplete) notes
abo
> On Dec 21, 2021, at 2:53 PM, Rudolf Adamkovič wrote:
>
> I struggle to understand. Why do we need a customization? If Org knows
> that some backend exists but has no execute function, why does it even
> try to execute it? It cannot. Do I miss something?
Sorry if my prior posts were garb
On Tuesday, 21 December 2021 20.07.01 -03 Rudolf Adamkovič wrote:
> Felipe Lema writes:
>
> > Sup, y'all
> >
> > I started using guile with Org Babel […]
>
> Sup! I plan to write some literate Scheme soon as well. How do you find
> the experience so far? As of today, I use 'scheme-mode' with a
26 matches
Mail list logo
