I've seen a number of people note how slow loading of BibTeX files is in
oc-basic.
Just wondering: do we know why, and whether there are opportunities to
improve it?
For comparison, parsebib (which I use in citar) is much faster.
Bruce
> So the problem is in (org-user-idle-seconds), which in my window system
> boils down to a call to (current-idle-time). It should return 0 after
> answering the prompt, but in my system it keeps counting up. At this
> point I stopped investigating since that function is defined in C.
>
I have in
"Barton, Mark" writes:
> I manually check the pdf to see if it fits and use a code formatter to get the
> line widths shorter. I use blacken for python and sqlformat for SQL within
> Emacs. Even then I still hit limits where I recently changed to font size to
> small for the code blocks.
>
> I
I manually check the pdf to see if it fits and use a code formatter to get the
line widths shorter. I use blacken for python and sqlformat for SQL within
Emacs. Even then I still hit limits where I recently changed to font size to
small for the code blocks.
I use minted for syntax highlighting
Kaushal Modi writes:
> Well, that will at least help the code blocks going out of bounds. It
> won't help the quotes.
With the quotes going out of bounds issue it would be nice to see a
screenshot. But if a line of normal text goes outside the margin, it is
usually due to a TeX overfull hbox, pe
> When I export an Org file to LaTeX and finally PDF, the code blocks and
> quotes often exceed the width of the page.
> Is it possible to set some style of the exported blocks ?
I wonder what the export engine can do about code which is too wide? As a
programmer, I certainly wouldn't like some
On Sun, Mar 13, 2022, 6:55 AM Sébastien Gendre wrote:
> Hello everyone. _o/
>
> When I export an Org file to LaTeX and finally PDF, the code blocks and
> quotes often exceed the width of the page.
>
Hello _o/
I fixed[1] that problem by using the LaTeX minted package that allows
wrapping around
On Sun, Mar 13, 2022, 8:23 AM wrote:
> In real I (try to) use ox-hug to export my org-files (org-roam-v2) to
> markdown (and later to HTML).
>
> After analyzing the my debug output [1] the ox-hugo people pointed me to
> org-roam community because the error is "thrown" (correct term in
> emas-lisp
Samuel Wales writes:
> are there intereim workarounds like semi-automatically moving large
> logbook entries, or entire logbooks, to a task that says "was logbook
> for ..." and then archiving that task? or automatically archiving old
> logbook entries?
My largest logbook contains ~2.5k clock
In real I (try to) use ox-hug to export my org-files (org-roam-v2) to
markdown (and later to HTML).
After analyzing the my debug output [1] the ox-hugo people pointed me to
org-roam community because the error is "thrown" (correct term in
emas-lisp=?) by "org-export-resolve-fuzzy-link".
"org-expo
Hi Thierry,
thanks for your feedback and please let me know if I should change
anything to fit
better into the org-mode codebase.
> Easily adding DLang dependencies while keeping a single code block seems
> quite useful.
> I will take a deeper look at your proposal.
> Also, you marked your patc
Hello everyone. _o/
When I export an Org file to LaTeX and finally PDF, the code blocks and quotes
often exceed the width of the page.
Is it possible to set some style of the exported blocks ? Like we can set the
size for images ? I can't found it.
Thanks for your help.
Séb
12 matches
Mail list logo
