Kyle Meyer writes:
> Jorge P. de Morais Neto writes:
>
>> Hi. The HTML export has JavaScript that LibreJS does not recognize as
>> free.
>
> Thanks for noting this. That's certainly not ideal.
>
>> My first attempt at an workaround (inspired by the Org Mode mailing
>> list) was merely
Aloha Kyle,
Thanks for this. I think the Worg list might be useful to
indicate which languages don't have maintainers. Or, is the
information in the source files sufficient? I'm happy not to work
on the Worg table in that case.
All the best,
Tom
Kyle Meyer writes:
Thomas S. Dye
Hi Eric,
Thanks for writing in and sharing your thoughts. I have some specific
comments that you may find below, but more generally: I get the
impression you approached this from the view of Org development and
patch merging.
In short, while I appreciate that Org development should be a
Here's another patch to remove some more use of the old dynamically
scoped dialect of ELisp.
Stefan
* lisp/ox.el: Fix various uses of the non-lexical-binding ELisp dialect.
(org-export--get-global-options, org-export-insert-default-template):
Use lexical-binding.
Oorja Sandhu writes:
> Steps :
> 1. emacs -Q
> Latest Emacs cloned and built from master today.
>
> 2. Open the attached org file
>
> 3. M-x org-table-header-line-mode
>
> 4. M-x org-indent-mode
>
> 5. Resize emacs window very small such that horizontal as well as vertical
> scrolling is
Yaroslav Rogov writes:
> Currenty there’re following lines in org-mouse.el:
>
> (font-lock-add-keywords
>nil
>`(("^[ \t]*\\([-+*]\\|[0-9]+[.)]\\) +\\(\\[[ X]\\]\\)"
> (2 `(face bold keymap ,org-mouse-map mouse-face highlight)
> t)))
>
Jorge P. de Morais Neto writes:
> Hi. The HTML export has JavaScript that LibreJS does not recognize as
> free.
Thanks for noting this. That's certainly not ideal.
> My first attempt at an workaround (inspired by the Org Mode mailing
> list) was merely encoding the ampersand in the magnet
Thomas S. Dye writes:
> Aloha all,
>
> Is there a list of current ob-* maintainers?
Bastien updated the "Maintainer" field of the source files:
$ git grep -i maintainer lisp/ob-* | cut -d'<' -f1
lisp/ob-C.el:;; Maintainer: Thierry Banel
lisp/ob-J.el:;; Maintainer: Joseph Novakovich
Tim Visher writes:
> On Wed, Jan 20, 2021 at 11:10 PM Kyle Meyer wrote:
>>
>> It's been applied to master (f4b9f9808). Please report back if you
>> still encounter the problem in your use case.
>>
>
> I (finally) got around to testing this out. Initially I thought it had been
> released in
thank you. i use export. e.g. export a subtree to html and paste
into blogger. i don't use publish.
for me [and some others on this thread iirc] tec's fix looks good,
fwiw. it would not proliferate custom id or id, and would fix both.
On 4/18/21, Nicolas Goaziou wrote:
> Hello,
>
> Samuel
David Masterson writes:
> Tim Cross writes:
>
>> I suspect the best model for moving forward is for new features and
>> enhancements to be initially implemented as add on contribution packages
>> rather than as extensions/enhancement to the core 'org-mode' package.
>> Such packages, if found
Hi Tim,
Another data point from me. I agree with your concerns, although they are
difficult to solve! Since we're talking about voluntary work and non-paid work.
And maintenance can take a lot of time and effort.
This is not the first time this topic comes up on the list. Both you and me
took
You didn't ask me, but since I'm currently here and reading the list I might
just give 2c to the topic.
My understanding is that a BNF-grammar is virtually impossible for Org. The org
language is ambiguous and writing a context free grammar for it hence is not
possible. For reference, see [1].
Tim Cross writes:
> I suspect the best model for moving forward is for new features and
> enhancements to be initially implemented as add on contribution packages
> rather than as extensions/enhancement to the core 'org-mode' package.
> Such packages, if found to be popular or useful to a large
James Powell writes:
> If I put #+name before the table, the link does indeed work, but now
> the table is reproduced twice in the latex output and also C-c C-c in
> the code block writes a new table into the file instead of updating
> the current table.
>
> Before C-c C-c in the code block,
If I put #+name before the table, the link does indeed work, but now
the table is reproduced twice in the latex output and also C-c C-c in
the code block writes a new table into the file instead of updating
the current table.
Before C-c C-c in the code block, this org snippet produces the table
Tom, thanks! i assumed something like that.
Maxim Nikulin writes:
> On 19/04/2021 23:08, Nicolas Goaziou wrote:
>>> + ;; Space role in sorting.
>>> + ;; Test would fail for locales with ignored space, e.g. en_US, it
>>> works
>>> + ;; in C and currently rare locales having significant space (es_ES,
>>> pl_PL)
>>> +
Hello,
James Powell writes:
> Using Org mode version 9.4.4 I build this document:
>
> <>
>
> #+NAME: t1
> #+begin_src R :exports both
>
> library(tidyverse) x <- tribble(~a, ~b, 1, 3) x #+end_src
>
> #+CAPTION: Org Table
> #+RESULTS: t1
>
> | 1 | 3 |
>
> I want to refer to Table [[t1]].
On 19/04/2021 23:08, Nicolas Goaziou wrote:
+ ;; Space role in sorting.
+ ;; Test would fail for locales with ignored space, e.g. en_US, it works
+ ;; in C and currently rare locales having significant space (es_ES,
pl_PL)
+ (should
+ (equal "- Time stamp\n- Timer\n"
+
Using Org mode version 9.4.4 I build this document:
<>
#+NAME: t1
#+begin_src R :exports both
library(tidyverse)
x <- tribble(~a, ~b, 1, 3)
x
#+end_src
#+CAPTION: Org Table
#+RESULTS: t1
| 1 | 3 |
I want to refer to Table [[t1]].
<>
What I expect: the latex export will include the table
Hi Greg,
seq cannot be used because it is not available in older versions
of emacs that org still supports. When support for those older
versions is dropped then seq could be used. Best,
Tom
hi, Nicolas,
i'm curious, not knowing history and/or procedures.
> ... CL is still necessary however, as we cannot use `seq' yet.
why is 'seq not "yet" available? what will make it available?
cheers, Greg
Hello,
Maxim Nikulin writes:
> Just a curiosity, what is style guide recommendation: let - lambda or
> cl-labels?
I stay away from CL as much as possible, otherwise newcomers will have
to learn two languages to start contributing, Elisp and CL (cl-loop,
ewww). CL is still necessary however, as
Hi Nicolas,
> Don't you need to simply move point within the entry and use `ancestors'
> view?
Yes, but that would work only for one entry. My main use case is to first
filter tree by `org-sparse-tree', then export all filtered contents with
`visible-only' option. If I am to use `ancestors'
On 2021-04-19, 10:19 +0200, Nicolas Goaziou wrote:
>> My previous patch proposed to add support for importing file with
>> arbitrary name and building upon that this patch tries to make use of it
>> by making org-table-import smarter by simply adding more separators
>> (delimiters).
>
> Good
Heh, I just found myself wanting to do this. I often use C-c ^ to sort
subtrees by creation date, and I wanted to do that with my global TODO
list just now, but couldn't figure out how.
So, imo there is at least a small need for this feature.
signature.asc
Description: PGP signature
Hello,
Ramesh Nedunchezian writes:
> When I export the following snippet, I get an error. See attachments
> for details.
>
> * Commands in library ~helm-sys~
>
> ** top
>:PROPERTIES:
>:DESCRIPTION: Brief summary of what Org does.
>:END:
I think this is a
On 19/04/2021 15:33, Nicolas Goaziou wrote:
Could you try the following instead?
--8<---cut here---start->8---
(defun org-sort-remove-invisible (s)
"Remove invisible part of links and emphasis markers from string S."
(let ((remove-markers
* org-protocol (org-protocol-capture): Add missing plus-sign to
javascript snippet to allow readers of the doc string to use example
snippet with minimal edits.
TINYCHANGE
---
lisp/org-protocol.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org-protocol.el
When I export the following snippet, I get an error. See attachments
for details.
* Commands in library ~helm-sys~
** top
:PROPERTIES:
:DESCRIPTION: Brief summary of what Org does.
:END:
- ~helm-top~ ::
#+findex: helm-top
#+kindex: C-x c t
Hello all,
I've avoided saying anything in this discussion but not from lack of
empathy with the initial post. Many valid points have been made in the
thread and I understand the frustrations. My own view is that org is
now at a different stage than it was some years ago. It is a
feature-full
Hello,
Ramesh Nedunchezian writes:
> Thanks for the feedback. I would be most happy if you could borrow
> ideas from my patch. (The changes are really small.)
Sorry, my plate is full already. Maybe someone else will want to give it
a try.
> Additional notes:
>
> 1. I didn't have information
Hello,
Maxim Nikulin writes:
> On 05/04/2021 06:06, Nicolas Goaziou wrote:
>> Joost Kremers writes:
>>
>>> I tend to agree that allowing local modifications of Org's syntax is pretty
>>> much
>>> pointless, but then why is `org-emphasis-alist` a user option?
>> In practice, the faces, i.e.,
Hello,
Juan Manuel Macías writes:
> I would like to propose this (possible) patch.
>
> With `#+STARTUP: macro-arg-sep-other' the macros arguments can be
> separated by a string other than comma, whose value is defined in
> `org-macro-arg-sep-other' (by default it is "'@").
Even though Org
Hello,
Juan Manuel Macías writes:
> I wonder if this other approach can be viable or if it is something
> crazy: if the spaces in org-sort-remove-invisible are a
> problem only for the first emphasis of each item, how about this
> fix to org-sort-list? (not modifying org-sort-remove-invisible):
Hello,
Cheong Yiu Fung writes:
> Hi, I'm proposing a new option in `org-show-context-detail', which shows
> current headline, its ancestors, *and the entry itself*. This is useful
> when export matched subtrees and their contents quickly with least
> manual intervention.
>
> Consider when
Hello,
Utkarsh Singh writes:
> My previous patch proposed to add support for importing file with
> arbitrary name and building upon that this patch tries to make use of it
> by making org-table-import smarter by simply adding more separators
> (delimiters).
Good idea, thank you. Some comments
Hello,
Erik Hetzner writes:
> Subject: [PATCH] manual: Fix publish options
>
> * doc/org-manual.org (Publishing sample configuration):
> * doc/org-guide.org (Publishing):
> Fix stylesheet setting in publish: :style is not a valid option; use
> :html-head instead. :table-of-contents is not a
Hi Tom,
Thank you for the comments.
Tom Gillespie writes:
> All of the issues that I'm aware of are related to what
> happens if tangling fails part way through the process.
That's not something I had considered. I wrote a new version of the
patch (attached) which addresses the insecure
40 matches
Mail list logo
