Attached is an updated patch that renumbers footnotes since a few footnotes
were removed with the table.
On Wed, Nov 4, 2020 at 8:39 AM ian martins wrote:
> The language list in the manual is missing many languages. Rather
> than trying to keep the list up to date in two places that link to
>
Hi again,
While fixing other issues in the code I found thing worth improving. Thought to
just briefly mention it here as well, for full transparency.
`org-goto-first-child' now understand what a child is when before first
heading. This is inline with how other outline functions behave.
Since
Hi Kyle,
And thanks for a second pair of eyes on this!
I've pushed a patch to the repo that should fix it.
--- commit 8d7a9b4ce
Hide drawers before first headline properly when cycling visibility
* lisp/org.el (org--hide-drawers): New internal function consolidating
logic from two places
Hi Kyle,
> As a projectile user, I'm tempted to suggest that, instead of the adding
> the `project' value, org-insert-link could learn to call
> org-link-file-path-type if it is a function and, if that returns
> non-nil, do the prefix check. Then projectile users could set it to
>
Hi, A patch is applied to master (commit 19d2f79a0) in order to speed up the
rebuilding of ID locations.
Performance testing on my own setup shows a huge reduction in time to rebuild
the cache. It goes from 168 seconds to 3 seconds. This performance increase is
not to be expected for all
---
doc/org-manual.org | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index ef2dad9ef..e78690993 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -5741,6 +5741,7 @@ expressions to process these values before inserting them
The language list in the manual is missing many languages. Rather
than trying to keep the list up to date in two places that link to
each other, this removes the list from the manual which is updated
less frequently.
The languages page was moved in Worg to make it the index page in the
languages
Hi Palak,
Palak Mathur writes:
> Paperwork with FSF is now complete.
Thanks! I've added you as a maintainer for ob-groovy.el.
Let me know (privately) what username you want for your account
on https://code.orgmode.org.
Best,
--
Bastien
I think we may be able get something promising by merging your
(Christian + Tom) ideas and David's. What if we have have a
#+TBLCELLMERGE key which acts as you describe, and /just using the
current table syntax/ have something like this (using the example
from
my first email)
| a | b | c |
+1 for enabling table-cell merges in export. I imagine this would be a
tricky job for developers, but it would relieve me as a user of much
repeated fiddling with exported drafts.
+1 for doing it without adding clutter to the table syntax, but
specifying merges on a separate line like formulas,
10 matches
Mail list logo
