The exported html from Org Mode contains a style for element pre.src,
overflow: visible. This causes code elements with reasonably
long lines to extend out of the box boundaries, causing a horizontal
scroll of the document.
Changing overflow: visible to overflow: auto
should solve this, making the
Hi!
I think the subject of the post says it all. While using org-mode I often have
a lot of LaTeX fragments scattered in my documents for mathematics, and I
typically use the startup functionality to load all those previews when a file
is loaded.
Due to this, I'd be really interested in seeing
I'd rather support this change, as I don't have TAB on my keyboard, I
use C-i instead of TAB
OTOH, C-M-i , which is essentially M-TAB, and essentially what the
changes is supposed to be, if flyspell-auto-correct-word (found in
flyspell-mode-map)
So, if this change is made, and flyspell is turned
Ihor Radchenko writes:
>> It looks like an oversight to me. I think
>> org-startup-with-latex-preview should be let-bound to nil around
>> org-goto-location's call to org-mode. Likewise, I'd say that
>> org-startup-with-inline-images and org-startup-shrink-all-tables should
>> be let-bound to ni
> It looks like an oversight to me. I think
> org-startup-with-latex-preview should be let-bound to nil around
> org-goto-location's call to org-mode. Likewise, I'd say that
> org-startup-with-inline-images and org-startup-shrink-all-tables should
> be let-bound to nil.
Is there even a need to c
Vladimir Nikishkin writes:
> Why is it that org-goto enforces the regeneration of previews in a buffer?
It looks like an oversight to me. I think
org-startup-with-latex-preview should be let-bound to nil around
org-goto-location's call to org-mode. Likewise, I'd say that
org-startup-with-inline
Sébastien Miquel writes:
> Is there a way to have an org-babel block which only exports its code
> but still gets evaluated when exporting ?
I think you can do something like this:
#+begin_src emacs-lisp :exports both :results none
(setq my-variable t)
#+end_src
Or, if you want to pas
Hello, everyone!
Below is an excerpt of the profiler report after typing C-c C-j:
- command-execute2385 76%
- call-interactively2385 76%
- funcall-interactively
Kevin Foley writes:
> The attached patch kills the buffer of the file modified
> during testing to prevent leaving the repo in a dirty state.
Thanks. I applied it in 7a2b785d6 with a small tweak so that a buffer
rather than a buffer name is passed to kill-buffer. In the context of
the tests, th
The attached patch kills the buffer of the file modified
during testing to prevent leaving the repo in a dirty state.
Thanks to Kyle for seeing this and providing guidance on how to
address.
Thanks,
Kevin
>From 46dd1cf3c34a372612e4a67a79afd84ca3317500 Mon Sep 17 00:00:00 2001
From: "Kevin J. Fo
On 5/22/20 11:10 AM, Bastien wrote:
> If you think it is useful as a patch against Org, not just as a way to
> customize a setup, can you send a patch?
>
> See https://orgmode.org/worg/org-contribute.html on how to contribute.
Ok, it is on my list, thanks.
--
Anthony Carrico
Alejandro,
Have you tried ox-hugo? There's an org exporter to Hugo. I use it and it works
pretty much flawlessly.
--
James Miller
james.ryland.mil...@gmail.com
Hi Thomas,
Thomas Schaper writes:
> When playing around with org-archive, I noticed that the function
> org-archive-all-matches doesn't use org-archive-default-command but
> calls org-archive-subtree directly. Is there any reason for this, or is
> it simply a small bug/missing feature?
I think
Hello,
TEC writes:
> Ok, I think this is everything except for except putting (length
> contents) in a let binding. I don't mind if you edit a let binding
> into the patch, I'm just struggling to overcome a feeling that it's
> a bit silly adding a binding for a short, simple function called
> tw
Anthony Carrico writes:
> Given that the mailing list holds the issues, it would be nice if you
> could import the mailing list into your client as a lump (maildir/mbox).
> Currently you can only download it chunk by chunk, so it isn't really
> practical for a newcomer to import the whole list
Hello Bastien,
I have now signed the FSF papers. Here is the updated patch on top of
current master.
Let me know if all looks good or if I need to make further changes or
need to provide something else.
Best regards,
Terje
On Mon, Feb 17, 2020 at 12:29 AM Bastien wrote:
>
> Hi Terje,
>
> Terje
Detlef Steuer writes:
> How to add more now? Same here. Mail is functionally superior to a lot
> of modern solutions.
>
> A Bugtracker you do not use on a regular basis often is a horrible time sink.
> Plus, most of the time you need just another account for a site you
> never wanted an account o
Timothy writes:
> Nicolas Goaziou writes:
>
>> Thank you. It looks fine, I will only be nitpicking.
>
> Nitpick away :D
>
>>> +(defun org-edit-latex-fragment ()
>>> + "Edit LaTeX fragment at point."
>>> + (interactive)
>>> + (let* ((context (org-element-context))
>>> +(_ (unless (and (e
I think another way to do it is to have an #+attr_org: :width as the
first attribute.
Vladimir Nikishkin writes:
> At the moment, I'm working around this by setting the width in "TeX points":
>
> #+attr_latex: :width 224pt
>
> The exported image becomes 224 points wide (roughly 8 cm), and the
>
On Friday, 22 May 2020 at 16:14, Bastien wrote:
> I see there is
> https://github.com/msherry/ical2org/blob/master/ical2org.awk
Interesting. I hadn't been aware of that fork.
> so perhaps hosting the code on worg/code/ is not so useful
> anymore?
I don't really have a strong opinion about thi
Ok, I think this is everything except for except putting (length
contents) in a let binding. I don't mind if you edit a let binding
into the patch, I'm just struggling to overcome a feeling that
it's a bit silly adding a binding for a short, simple function
called twice.
Let me know if this
> On Mon, 25 May 2020 13:20:30 +0200, Roland Everaert
> said:
Roland> No, I was not aware of it. Yet, if I understand the objective of
the Emacs
Roland> ML and Debbugs, it is for, when you have a crash with emacs or, at
least,
Roland> an error stack trace when evaluating s
Nicolas Goaziou writes:
Without hesitation, the first form is nicer. The second one is
just abusing let-binding. I die a little just by looking at it.
I'll make an attempt to avoid killing you then :P
See `rx' macro. S-exp regexps are usually easier to read (after
an initial struggle), a
Timothy writes:
> I had a look at that, to me this was cleaner than using multiple let
> bindings, like so
>
> (let ((context ...))
> (unless ... user error)
> (let* ((contents ...)
> (delim-length ...))
>...
>
> vs.
>
> (let* ((context ...)
>(_ (unless ... user error))
Nicolas Goaziou writes:
> Thank you. It looks fine, I will only be nitpicking.
Nitpick away :D
>> +(defun org-edit-latex-fragment ()
>> + "Edit LaTeX fragment at point."
>> + (interactive)
>> + (let* ((context (org-element-context))
>> + (_ (unless (and (eq (org-element-type context) 'la
Hello,
Ihor Radchenko writes:
> I have five updates from the previous version of the patch:
Thank you.
> 1. I implemented a simplified version of element parsing to detect
> changes in folded drawers or blocks. No computationally expensive calls
> of org-element-at-point or org-element-parse-b
Hello,
TEC writes:
> ---
> lisp/org-src.el | 45 +
> lisp/org.el | 1 +
> 2 files changed, 46 insertions(+)
Thank you. It looks fine, I will only be nitpicking.
> +(defun org-edit-latex-fragment ()
> + "Edit LaTeX fragment at point."
> + (int
27 matches
Mail list logo
