nt this approach, but it seems quite easy to break
other parts of Org in the process. Would you mind guiding me on how to
implement it properly?
Best regards,
Lei
On Sun, Jun 8, 2025 at 8:07 PM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> > Yes, this definitely makes sense, but we
initely makes sense, but we need to get rid of the
`only-this-block` parameter here, since the result of
`org-babel-tangle-single-block` needs to be a nested list. This must
be a breaking change that we discussed before.
I'll address the other issues you mentioned in the last email.
Regar
ult becomes ambiguous.
2. As I mentioned, I'm unsure how to handle the output of
org-babel-tangle--unbracketed-link for its use in
org-babel-tangle-comment-links.
I'm open to suggestions.
llcc
On Sun, Apr 13, 2025 at 1:24 AM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> >
> how can users of `org-babel-tangle-single-block' figure out which variant of
> the return value is to expect?
It returns the correct relative or absolute link that users can expect
when :tangle is a single path, while it returns an absolute link when
:tangle is a list.
It’s a tradeoff, though, b
oops, the logic is incorrect, please check the new patch.
llcc
On Sat, Mar 22, 2025 at 9:13 AM Lei Zhe wrote:
>
> Thanks for your suggestion. Or, return bare only if :tangle has
> multiple targets in `org-babel-tangle--unbracketed-link', then we
> can leave everything else un
wrote:
>
> Lei Zhe writes:
>
> > Then, for the returned value `result' of org-babel-tangle-single-block:
> > The original function returns (file-name1 ... link1 ...).
> > The proposed function returns ((file-name1 ... link1 ...)).
> >
> > If we chang
2025 at 1:03 AM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> >>> you can simply return multiple (file-name src-lang start-line file link
> >>> source-name params body comment) items.
> >>> (file-name1 ... link1 ...)
> >>> (file-name2 .
ot changed.
((file-name1 ... link1 ...)
(file-name2 ... link2 ...))
llcc
On Wed, Mar 19, 2025 at 1:54 AM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> > I realized that it's challenging to handle the error properly if the
> > return value of org-babel-tangle-sing
aking one, I'd like to hear your
thoughts. Do you have any suggestions for handling this more
effectively?
llcc
On Tue, Mar 18, 2025 at 1:59 AM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> >>>As for the patch, I tried to run it with simple example and got an error.
&
b-tangle.el.
Where is their logic implemented in ob-tangle.el?
llcc
On Sat, Mar 15, 2025 at 9:55 PM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> >>> With this change, ONLY-THIS-BLOCK = nil is ignored. This will cause
> >>> problems.
> > I intended to remove the ON
ly be abandoned if the patch gets accepted.
llcc
On Wed, Mar 12, 2025 at 4:38 AM Phil Estival wrote:
>
> References:
>
>
> User-Agent: mu4e 1.12.8; emacs 30.1
> Date: Tue, 11 Mar 2025 21:38:00 +0100
>
> * [2025-03-09 15:12 +0800] Lei Zhe :
>
> Hello Lei,
Since Phil hasn't responded for almost two weeks,
I would like to submit the patch first.
This patch is the first step in resolving the feature for tangling
source blocks to multiple targets.
I would appreciate any feedback.
llcc
On Sun, Feb 23, 2025 at 9:05 PM Lei Zhe wrote:
>
&
Hi Phil,
Thank you for sharing the proposal and patch.
It'll make the tangle system more flexible, and I would be glad to
see it included in the next release. As it has been some time since
your last response, I wanted to check in to see if you’re still planning
to complete the patch. If not, I
Yes, it makes sense. I'll go ahead and reconsider how to do it without
implication.
On Sun, Feb 16, 2025 at 12:06 AM Ihor Radchenko wrote:
>
> Lei Zhe writes:
>
> > When a source block is indented within a list, as shown below,
> > even if I set `org-fontify-whole-bl
oops, typo. The faces shouldn't be applied to spaces.
On Thu, Feb 6, 2025 at 8:47 PM Lei Zhe wrote:
>
> When a source block is indented within a list, as shown below,
> even if I set `org-fontify-whole-block-delimiter-line` to nil, the
> spaces before `#+begin_src` are still fo
When a source block is indented within a list, as shown below,
even if I set `org-fontify-whole-block-delimiter-line` to nil, the
spaces before `#+begin_src` are still fontified if I have custom
faces for `org-block-begin-line` and `org-block-end-line`. In my
opinion, this is incorrect behavior; th
Sorry, it was [[attachment:example.pdf::2]].
The lint for [[file:example.pdf::2]] is fine, since
org-element-context returns the raw path without the search option.
However, this is not the case for [[attachment:example.pdf::2]].
On Sun, Jan 19, 2025 at 5:57 PM Ihor Radchenko wrote:
>
> L
For the link [[file:example.pdf::2]], org-lint identifies it as an invalid link.
This patch aims to address the issue.
0001-Check-local-file-link-ignoring-path-option.patch
Description: Binary data
Great, thanks.
On Sat, Apr 13, 2024 at 2:04 AM Ihor Radchenko wrote:
> Bastien Guerry writes:
>
> > Ihor Radchenko writes:
> >
> >> P.S. Bastien, may your please check Lei Zhe's copyright status?
> >
> > Yes, I confirm Lei Zhe copyright status is o
able-begin' to get the beginning position
of the table at WS, regardless of the cursor position, resolves the
above problem.
Regards,
Zhe Lei
On Sat, Apr 6, 2024 at 2:40 AM Ihor Radchenko wrote:
> Lei Zhe writes:
>
> > The patch ensures the header of an org-table displays witho
Hi org-mode community,
The patch ensures the header of an org-table displays without the cursor
inside the table when org-table-header-line-mode is enabled.
BTW, this is my first patch for org-mode, so please correct me if there
are any issues with it.
Also, I've done the paperwork before.
Regar
wrote:
> Hello,
>
> Lei Zhe writes:
>
>> I tried to exclude the table export of one headline by setup:
>>
>> * headline
>> :PROPERTIES:
>> :EXPORT_OPTIONS: |:nil
>> :END:
>>
>> But the string nil error appeared.
>> Any help?
I tried to exclude the table export of one headline by setup:
* headline
:PROPERTIES:
:EXPORT_OPTIONS: |:nil
:END:
But the string nil error appeared.
Any help?
I am working on Org-mode 8.2.10.
Zhe Lei
I have some subscripts in my org file like B_25, B_30. These
subscripts can be exported to LaTeX like B_{25}, B_{30}. However, I
want part of the subscripts like B to be exported as italic /B/. As
one solution for this, I can wrap these thing into a math environment
like \(B_{25}\). But since my fi
large
numbers of footnotes.
Regards,
Zhe Lei
On Thu, Aug 6, 2015 at 9:33 PM, Nicolas Goaziou wrote:
> Lei Zhe writes:
>
>> Hi, I tried to customize `org-footnote-auto-adjust'.
>> There are only kind of sort and renumber options.
>> None of them can make the footno
Hi, I tried to customize `org-footnote-auto-adjust'.
There are only kind of sort and renumber options.
None of them can make the footnote appear at the end of `Footnotes' section.
Regards,
Zhe Lei
On Thu, Aug 6, 2015 at 9:18 PM, Nicolas Goaziou wrote:
> Hello,
>
> Lei
I found two bugs if the latest org-mode 8.3.1.
1. Footnote is inserted right after the Footnote headline, not the end
of this section.
2. When I call org-drill, some entries can not be shown. Only blank
buffer shows up.
Hope these bugs can be fixed.
Dear orgers,
I read the export option part in org manual, but i could not find the
option for excluding the internal links for LaTeX export.
Is there any other idea to do this?
Thanks ahead of time.
Dear orgers,
I am trying to export a beamer from org-mode with my own \author
command defined.
But when I export, org-mode always generates another \author after my
\author, which destroys the author list.
I tried:
1. #+author:
2. #+bind: latex-export-with-author ""
3. move #+author before my auth
29 matches
Mail list logo
