Hi,
Here's a tiny syntax fix in org manual.
YiufungFrom 2b63acfdb9f48fd48bce180f4894ed89b3910fe3 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Date: Tue, 27 Apr 2021 10:10:14 +0800
Subject: [PATCH] org-manual.org: Fix syntax
* doc/org-manual.org (HTML export commands): Fix kbd represent
s is to
facilitate using tag or TODO keyword to choose what tree to be shown.
YiufungFrom 5fdbffd88f573f132ace4bae2f1665e325bca3a4 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Date: Thu, 22 Apr 2021 23:25:03 +0800
Subject: [PATCH] org-manual.org: add hints for visible-only export
---
doc/org-manual.org | 2 +-
1 file ch
Hi Nicolas,
On Wed, Apr 21, 2021, at 5:15 PM, Cheong Yiu Fung wrote:
> The first patch implements the changes. I took the liberty to show
> entry of its ancestors
> too (4 in the test case). Many users, I believe, rarely put text there,
> so it does not
> make a difference.
Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Date: Wed, 21 Apr 2021 16:26:14 +0800
Subject: [PATCH 1/2] org.el (org-show-context-detail): add option
'ancestors-full
* lisp/org.el: Add option 'ancestors-full to
`org-show-context-detail', update `org-show-set-visibility'
acco
Nicolas Goaziou wrote:
> Hello,
>
> "Cheong Yiu Fung" writes:
>
> > 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
If I am to use `ancestors' view and move point within
each entry one by one to expand, it would be very repetitive. I think this is
helpful for generating HTML page or PDF from matching query quickly.
Yiufung
On Mon, Apr 19, 2021, at 4:21 PM, Nicolas Goaziou wrote:
> Hello,
>
>
some difficulties to
updating documentations, so I wish to have some feedbacks before moving
on. Is there better way to achieve this effect? Am I overlooking
something?
Yiufung
>From 38703eace6062ec4e4ccdf1912a641b266efbf61 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Date: Fri, 16 Apr 2021 18:35:17 +
Hello,
Here's a patch to quote output file name following the fashion of input file
name as used in `org-odt-convert'. It avoids conversion errors in the
underlying shell commands.
YiufungFrom e77284cc511afc9d3e9ad68c9b36f9f69bcad413 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Hello,
Here's a patch to quote output file name following the fashion of input file
name as used in `org-odt-convert'. It avoids conversion errors in the
underlying shell commands.
YiufungFrom e77284cc511afc9d3e9ad68c9b36f9f69bcad413 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Hi,
When navigating using `org-babel-next-src-block`(C-c C-v C-n), if the next
source block is in an archived subtree, Org mode would expand it and move
cursor to it.
Is this an expected behavior / desired feature? It seems more natural to skip
source blocks that are under an archived subtre
This is really useful. Thanks!
Yiufung
On Tue, Dec 3, 2019, at 10:56 AM, Karl Fogel wrote:
> Hi. I've been using this for a while and find it very handy.
>
> If people like this and want it in Org Mode, I'll do the rest of the
> work to package it up as a patch, with ChangeLog entry, NEWS, etc
I'm using the latest Org and it's working. If you'd like to dig the
cause you might want to dig in `org-display-inline-images'. It accepts
`:width' in any #+ATTR.*-like option, then immediately call
`create-image'. I would guess it's an imagemagick problem too.
steen writes:
> I am also having t
Fix docstring of `org-latex-packages-alist'.
--
YiufungFrom f854de4a4570a433871a2559160a7499c4c054d7 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung
Date: Fri, 17 May 2019 17:15:43 +0800
Subject: [PATCH] org.el: Fix docstring of org-latex-packages-alist
* lisp/org.el (org-latex-packages-
* doc/org-manual.org (Handling Links): update variable
`org-id-link-to-org-use-id', which is changed in v7.9.2.
---
doc/org-manual.org | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 54b89e5bf..c519d310b 100644
--- a/
14 matches
Mail list logo
