Samuel,
since significant part of your message is dedicated to capturing of tab
groups I should ask if you have tried version of LinkRemark add-on
currently available from browser extension catalogues:
- https://addons.mozilla.org/firefox/addon/linkremark/
- https://chrome.google.com/webstore
On 18/01/2022 12:43, Samuel Banya wrote:
Not sure if it helps, but you could also use the w3m browser's mentality
of just keeping an HTML file that contains all of your bookmarks. I'm
sure there's probably even a way to use 'eww' in the same fashion too.
Maybe even making your own personal wik
Hi all,
I guess that I am not able to configure ox-context like this:
#+begin_src emacs-lisp
(use-package ox-context
:straight (ox-context :type git :host github :repo
"Jason-S-Ross/ox-context")
:config
(setq org-context-pdf-process '("context --mode=trimsize %f"))
(add-to-li
Tom Gillespie writes:
> Extremely in favor of removing switches. There are so many better ways
> to do this now that aren't like some eldritch unix horror crawling up
> out of the abyss and into the eBNF :)
I also agree that switches and $$-style equations may be deprecated.
We can
1. Do not men
Dejan Josifović writes:
> But, since ob-plantuml already had variable for arguments for executable
> it fells natural to me to have customizable variables for when using
> jar. These headers are of course easier, but the user would have to
> write them on each source block to achieve something
The code is the same as in v3, but I noticed that I had forgotten
to update one of the doc-strings, so that's fixed here.
Cheers,
Jonas
Jonas Bernoulli (3):
ox-texinfo: Add function for use by kbd macro
ox-texinfo: Optionally use @itemx for certain description list items
ox-texinf
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el: Add org-texinfo--combine-items to the list of
:filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--combine-items) New function.
* lisp/ox-texinfo.el
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el: Add org-texinfo--separate-definitions to the
list of :filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--quoted-keys-rege
* doc/doc-setup.org: Use org-texinfo-kbd-macro for kbd macro.
* doc/org-manual.org: Add new node "Key bindings in Texinfo export".
* lisp/ox-texinfo.el (org-texinfo-kbd-macro): New function.
---
doc/doc-setup.org | 2 +-
doc/org-manual.org | 27 +++
lisp/ox-texinfo.el | 2
As the subject line says. Missed it due to the plural tables... (my
bad).
Although I must add that I have spent some time playing with org babel
options and I am unclear about why ":results value verbatim" (or raw or
scalar or drawer) don't behave as I would have thought. But that's a
discussion
Dear all,
Should the export of a table that is the result of a code block and has
been wrapped in a RESULTS special block be different than one that is
not wrapped (beyond the wrapping, of course)? Specifically, wrapping
the results seems to cause org to ignore that ATTR_LATEX :center toggle
[1].
Eric,
> On Jan 18, 2022, at 9:05 AM, Eric S Fraga wrote:
>
> been wrapped in a RESULTS special block be different than one that is
> not wrapped (beyond the wrapping, of course)? Specifically, wrapping
> the results seems to cause org to ignore that ATTR_LATEX :center toggle
> [1]. A minimal e
Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.
On Mon, Jan 10, 2022, 08:53 Juan Manuel Macías
wrote:
> Hi,
>
> I have written for my personal use this code (still quite crude) that
> allows me to preview with org-latex-preview small text strings in a fon
Dear all,
I would like to tangle source code blocks that contain coderefs. I have
found that the coderefs are correctly filtered out from the tangled files
if they follow the default format, i.e. "(ref:%s)", but not if I try to
customize the format using the documented "-l" switch [1] to change th
Hello,
I was simply calling `org-agenda` when I was prompted to submit this report.
I'm submitting this as requested.
Thanks for all your good work on this,
APC
Emacs : GNU Emacs 28.0.90 (build 1, x86_64-apple-darwin19.6.0, NS
appkit-1894.60 Version 10.15.7 (Build 19H1419))
of 2021-12-14
Hi Ihor,
Thank you very much for the detailed responses. Let me start with
some context.
1. A number of the comments that I made fall into the brainstorming
category, so they don't need to make their way into the document at
this time. I agree that it is critical for this document to captu
Hi Luis,
I don't think you are doing anything wrong. IIRC the portion of the
patch that allowed the customization to propagate to the tangled code
was not included. Given that I am no longer the only one who is
looking for/expecting this behavior, maybe it is worth revisiting the
decision. The s
Max Nikulin writes:
> Scientific papers require more work, it is necessary to make them
> available to org-cite somehow. Some nerds use quite peculiar blog
> engines and strange setting of metadata. So shopping on some sites might
> work better than other cases.
I have plans to implement some
Alejandro Pérez Carballo writes:
> I was simply calling `org-agenda` when I was prompted to submit this report.
> I'm submitting this as requested.
Thanks for reporting!
If you keep seeing the warning, please followup this thread showing the
warning text. It will give us clues what went wrong
Hi Chuck,
On Tuesday, 18 Jan 2022 at 18:43, Berry, Charles wrote:
> This is annoying, but I think you can get the product you want by
> "pre-wrapping" the results.
Ah, I see: do the wrapping manually instead of using the :wrap header
argument. Yes, this works. A little annoying but it's a solut
20 matches
Mail list logo
