Hello,
Glenn Morris writes:
> Package: emacs,org-mode
> Version: 26.1.91
> Severity: minor
>
> The compiled file ox-odt.elc contains strings that refer to the
> absolute location of the build directory, through
> org-odt-schema-dir-list and org-odt-styles-dir-list.
> For example, in the Emacs
Package: emacs,org-mode
Version: 26.1.91
Severity: minor
The compiled file ox-odt.elc contains strings that refer to the
absolute location of the build directory, through
org-odt-schema-dir-list and org-odt-styles-dir-list.
For example, in the Emacs 26.1.91 pretest tarfile, it contains
Updating to the latest org-mode (9.2.1) seems to solve this issue.
On Sun, Feb 3, 2019 at 4:40 PM Abdo Haji-Ali
wrote:
> I just updated emacs to 27.0.50 and I am seeing the exact same error.
> I think org-preserve-local-variables is in org-macs which is part of
> org-mode source code.
>
> On
I just updated emacs to 27.0.50 and I am seeing the exact same error.
I think org-preserve-local-variables is in org-macs which is part of
org-mode source code.
On Sun, Feb 3, 2019 at 4:14 PM Kyle Meyer wrote:
>
> Hello,
>
> Abdo Haji-Ali writes:
>
> > On the latest org-mode version, 9.2, I
Hello,
Abdo Haji-Ali writes:
> On the latest org-mode version, 9.2, I keep receiving the error
> 'org-copy-subtree: Invalid function: org-preserve-local-variables'
> whenever I try to move a subtree or when I access my agenda.
>
> This happens even if I run emacs with '-Q'.
>
> Emacs : GNU
On the latest org-mode version, 9.2, I keep receiving the error
'org-copy-subtree: Invalid function: org-preserve-local-variables'
whenever I try to move a subtree or when I access my agenda.
This happens even if I run emacs with '-Q'.
Emacs : GNU Emacs 25.3.1 (x86_64-redhat-linux-gnu, GTK+
Robert Irelan writes:
> Patch to fix attached.
I can confirm that this patch is required to make `org-drill' work for me in
Org 9.2
Regards,
Stig
> From a3af9004fbc5a8a86ba8f990d393403ec671f9bf Mon Sep 17 00:00:00 2001
> From: Robert Irelan
> Date: Wed, 23 Jan 2019 11:11:14 -0800
>
Hi, could someone take a look at this? Other people have noticed this
issue: https://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00096.html
On Wed, Jan 23, 2019 at 11:18 AM Robert Irelan wrote:
>
> Patch to fix attached.
--
Robert Irelan
rire...@gmail.com
John Ciolfi writes:
> Hi
>
> Using following
>
> emacs -q --batch -L /path/to/org/install/emacs/site-lisp/org -l
> my-org-to-pdf.el
>
> the generated PDF is incorrect. The "compilation-minor" code block gets
> replaced with the "c" code block, i.e. the c code block is
> duplicated. If you
Hi
Using following
emacs -q --batch -L /path/to/org/install/emacs/site-lisp/org -l
my-org-to-pdf.el
the generated PDF is incorrect. The "compilation-minor" code block gets
replaced with the "c" code block, i.e. the c code block is
duplicated. If you generate HTML all is good. Running
I have the same issue with:
Org mode version 9.2 (9.2-43-gf9a8cc-elpaplus)
GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of
2018-12-14
I assumed it was a bug in comment-dwim-2, but it occurs with
comment-line too.
On 1/30/19 1:13 PM, Nicolas Goaziou wrote:
Hello,
Hello,
Spencer Russell writes:
> Thanks for trying it out. Would you mind sharing your emacs and org
> versions?
Sure.
Org mode version 9.2 (release_9.2-213-g5c07b4)
GNU Emacs 26.1
Could you try master branch?
Regards,
--
Nicolas Goaziou
On Tue, Jan 29, 2019, at 3:32 PM, Nicolas Goaziou wrote:
>
> FWIW, I cannot reproduce it.
>
Thanks for trying it out. Would you mind sharing your emacs and org versions?
-s
Hello,
Spencer Russell writes:
> I've been trying to troubleshoot an issue where running `comment-line`
> within a SRC block moves point to the beginning of the block, rather
> than after the commented line.
> I've boiled it down to a reproduction that duplicates the root cause.
> Open an org
Aloha all,
Answering myself. This bug is known and was discussed several years
ago:
From: Myles English
Subject: Re: [O] babel R: should/does order of parameters matter?
Date: Tue, 29 Mar 2011 16:57:37 +0100
Apparently, ob-R wants tables to be passed to parameters that are early
in the
Eric S Fraga writes:
> On Thursday, 24 Jan 2019 at 10:02, Nick Dokos wrote:
>> is* one with a caption). I do wonder why Eric and I could see it and
>> you could not, but some mysteries will remain despite one's best
>> efforts :-)
>
> Out of curiosity, I wonder if it's related to the version of
On Thursday, 24 Jan 2019 at 10:02, Nick Dokos wrote:
> is* one with a caption). I do wonder why Eric and I could see it and
> you could not, but some mysteries will remain despite one's best
> efforts :-)
Out of curiosity, I wonder if it's related to the version of Emacs? I'm
using
On Thursday, 24 Jan 2019 at 14:48, Nicolas Goaziou wrote:
> OK. I fixed that, even though I cannot reproduce the issue.
Thanks! Works fine now. Strange that you could not reproduce it.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2-207-g102142
Nicolas Goaziou writes:
> Hello,
>
> Nick Dokos writes:
>
>> Guessing the culprit is c28eb3c2cb904666594e40c1dcae4437d954bde4.
>> It seems that the caption is an empty string but the code tests whether
>> it's nil and since it isn't, it assumes there is a caption and makes it
>> into a floating
Hello,
Nick Dokos writes:
> Guessing the culprit is c28eb3c2cb904666594e40c1dcae4437d954bde4.
> It seems that the caption is an empty string but the code tests whether
> it's nil and since it isn't, it assumes there is a caption and makes it
> into a floating table.
OK. I fixed that, even
Remember to cover the basics, that is, what you expected to happen
and
what in fact did happen. You don't know how to make a good
report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Patch to fix attached.
From a3af9004fbc5a8a86ba8f990d393403ec671f9bf Mon Sep 17 00:00:00 2001
From: Robert Irelan
Date: Wed, 23 Jan 2019 11:11:14 -0800
Subject: [PATCH] org-drill: Fix tag match in org-map-drill-entries
* contrib/lisp/org-drill.el: Change MATCH argument to ORG-MAP-ENTRIES
from ""
Eric S Fraga writes:
> On Tuesday, 22 Jan 2019 at 23:52, Nicolas Goaziou wrote:
>> I cannot reproduce it. E.g.,
>> Would you have an ECM?
>
> Strangely, with attached ECM and emacs -Q, I have this problem. See
> attached resulting LaTeX.
>
> Thanks,
Guessing the culprit is
On Wednesday, 23 Jan 2019 at 15:21, Nicolas Goaziou wrote:
> Odd. Even with a minimal init file (i.e, I only loading Org), I cannot
> reproduce it.
Thanks Nicolas. It is indeed strange. I will play some more when I get
a chance (bogged down with work at the moment). As I have a way around
the
Hello,
Eric S Fraga writes:
> On Tuesday, 22 Jan 2019 at 23:52, Nicolas Goaziou wrote:
>> I cannot reproduce it. E.g.,
>> Would you have an ECM?
>
> Strangely, with attached ECM and emacs -Q, I have this problem. See
> attached resulting LaTeX.
Odd. Even with a minimal init file (i.e, I only
On Tuesday, 22 Jan 2019 at 23:52, Nicolas Goaziou wrote:
> I cannot reproduce it. E.g.,
> Would you have an ECM?
Strangely, with attached ECM and emacs -Q, I have this problem. See
attached resulting LaTeX.
Thanks,
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2-204-g3fc7b0
% Created
On Tuesday, 22 Jan 2019 at 23:52, Nicolas Goaziou wrote:
> I cannot reproduce it. E.g.,
> Would you have an ECM?
I did try essentially the same minimal example as you and it did not
work (i.e. table was wrapped in a table environment). I did not try with
emacs -Q however. I will do so when back
Hello,
Eric S Fraga writes:
> tables without captions now seem to export to tabulars within table
> environments, which they did not do before.
I cannot reproduce it. E.g.,
| a |
becomes
\begin{center}
\begin{tabular}{l}
\toprule
a\\
\bottomrule
\end{tabular}
Nicolas,
tables without captions now seem to export to tabulars within table
environments, which they did not do before. That is, before, a simple
table with no document exported to just a tabular environment. This
change is breaking many of my documents. Did I miss something or is
this
hello,
wlharv...@mac.com writes:
> The following Org document exports to Texinfo '.texi’ in Orgmode
> 9.1.14 but fails under Orgmode 9.2 with the following error message:
>
> 'Cannot generate node name for type: src-block'
>
> The source of the problem arises from commit `04f35fc473`. When the
The following Org document exports to Texinfo '.texi’ in Orgmode
9.1.14 but fails under Orgmode 9.2 with the following error message:
'Cannot generate node name for type: src-block'
The source of the problem arises from commit `04f35fc473`. When the
changes are undone in that one commit, the
Hello,
Alexandre Duret-Lutz writes:
> On Tue, Jan 15, 2019 at 11:50 PM Alexandre Duret-Lutz
> wrote:
>> Since I updated to org 9.2, the following idiom stopped working.
>>
>> --
>> #+NAME: context
>> #+BEGIN_SRC C++ :exports none
>> #include
>> int u = 0;
>> #+END_SRC
>>
>>
On 2019-01-19, at 16:06, Nicolas Goaziou wrote:
> Jens Lechtenboerger writes:
>
>> when exporting a table with caption to LaTeX on the master branch,
>> invalid code is generated.
>
> Fixed. Thank you.
Wow, that was lightning fast.
Many thanks!
Jens
Hello,
Jens Lechtenboerger writes:
> when exporting a table with caption to LaTeX on the master branch,
> invalid code is generated.
>
> Example Org file:
>
> #+CAPTION: Some text
> | Col1 | Col2 |
>
> |--+--|
> | foo | bar |
>
> The resulting tex file contains this, without table
Hi there,
when exporting a table with caption to LaTeX on the master branch,
invalid code is generated.
Example Org file:
#+CAPTION: Some text
| Col1 | Col2 |
|--+--|
| foo | bar |
The resulting tex file contains this, without table environment,
which is necessary for the use of
Thank you! I wasn't really sure what kind of function to pass to
add-variable-watcher, but using debug-on-variable-change, I got
the following output:
Debugger entered--setting org-stored-links to nil:
debug--implement-debug-watch(org-stored-links nil set nil)
org-insert-link(0 "test")
Hello,
· Nicolas Goaziou wrote:
> Thomas Holst writes:
>
>> recently I encountered a bug with capturing table lines. Here is a ECM
>> to reproduce it:
>>
> [...]
>
> Fixed. Thank you.
thank you! Works perfectly again.
--
Bis neulich ...
Thomas
Hello,
Thomas Holst writes:
> recently I encountered a bug with capturing table lines. Here is a ECM
> to reproduce it:
>
> - org-mode file (testing.org):
>
> #+begin_src org
> * Headline
> |---+--+|
> | | Name | Amount |
> |---+--+|
> |---+--+|
> | |
On Tue, Jan 15, 2019 at 11:50 PM Alexandre Duret-Lutz
wrote:
> Since I updated to org 9.2, the following idiom stopped working.
>
> --
> #+NAME: context
> #+BEGIN_SRC C++ :exports none
> #include
> int u = 0;
> #+END_SRC
>
> #+BEGIN_SRC C++ :exports both :noweb strip-export
Hello,
recently I encountered a bug with capturing table lines. Here is a ECM
to reproduce it:
- org-mode file (testing.org):
#+begin_src org
* Headline
|---+--+|
| | Name | Amount |
|---+--+|
|---+--+|
| | ||
|---+--+|
#+TBLFM:
I'm trying to create a custom agenda command that starts in follow-mode and
follows indirectly. Starting with follow mode works fine, but
org-agenda-follow-indirect is nil in the resulting org agenda buffer.
Minimal Working Example:
- save the following org txt as a local file
- evaluate the src
I think this is a bug but I don't know enough about svg images to be sure.
On export, links to svg images produce an element rather than an
. Here's the docstring of the function (from ox-heml):
-
Return \"object\" embedding svg file SOURCE with given ATTRIBUTES.
INFO is a plist used as a
Hi!
I have some documentation where I use the noweb syntax to include some
common context in some code fragment I want to discuss. On export
I'd like to display the code fragments without the common context,
followed by their output.
Since I updated to org 9.2, the following idiom stopped
Hi Kyle, org-mode developers,
* Kyle Meyer [2019-01-14; 17:10]:
> Kyle Meyer writes:
>> Gregor Zattler writes:
> [...]
>
>>> I did a git bisect on the org repo and got this:
>>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>>
>> Sorry, that certainly looks to be my fault
Kyle Meyer writes:
> Gregor Zattler writes:
[...]
>> I did a git bisect on the org repo and got this:
>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>
> Sorry, that certainly looks to be my fault (specifically, my conflict
> resolution merging maint's d64c9a996). I'll
Gregor Zattler writes:
> Dear org-mode developers, I did a git pull half an hour ago, now I
> cannot org-babel-load-file my configuration.org any more. Normally I
> use emacs as of git master but the (slightly different) error also
> occours with emacs 25.1.1 (as of currents debian stable) (see
On Mon, Jan 14, 2019 at 07:56:03PM +0100, Marco Wahl wrote:
> Hi,
>
> > no longer see the totals and org-clock-display produces the following
> > error message:
> >
> > Total file time: 0:00 (0 hours and 0 minutes)
>
> This is the expected behavior of the org-clock-display function AFAICS.
>
Hi,
> no longer see the totals and org-clock-display produces the following
> error message:
>
> Total file time: 0:00 (0 hours and 0 minutes)
This is the expected behavior of the org-clock-display function AFAICS.
See
C-h f org-clock-display
and
C-h v
Dear org-mode developers, I did a git pull half an hour ago, now I
cannot org-babel-load-file my configuration.org any more. Normally I
use emacs as of git master but the (slightly different) error also
occours with emacs 25.1.1 (as of currents debian stable) (see below).
I did a git bisect on
Hi all,
I've been using org-mode to perform the task of timesheets
with another GNU project and encountered something which has all the
hallmarks of a bug. I'm just not sure if it's a known issue or
whether to write up a bug report for it.
I use org-clock-in and org-clock-out to track
Thanks for the fix - I back-ported it to release_9.2 / 20181230 and it
works fine!!
... and thanks for the hard work of yourself and your team in bringing us
org-mode!!
Cheers
Bob
On Sat, 12 Jan 2019 at 20:50, Nicolas Goaziou
wrote:
> Hello,
>
> Bob Hepple writes:
>
> > In a prior version,
Hello,
david wen riccardi-zhu writes:
> Hello and thank you. This behavior did appear to be fixed, but it's
> surfaced once again today.
I couldn't reproduce it.
Regards,
--
Nicolas Goaziou
Hello,
Bob Hepple writes:
> In a prior version, when I clicked on a SCHEDULED: <...> link, it would
> popup the org-agenda view. Now (after a M-x package-list-packages U x)
> it does nothing and displays No link found. Is there a way to restore
> the old behaviour?
Fixed. Thank you.
Regards,
Hello and thank you. This behavior did appear to be fixed, but
it's surfaced once again today.
Nicolas Goaziou writes:
Hello,
David Wen Riccardi-Zhu writes:
I use the following capture template to store bookmarks:
* %^L :PROPERTIES: :NOTES: %^{NOTES} :END: :LOGBOOK: - Added
%U. :END:
In a prior version, when I clicked on a SCHEDULED: <...> link, it would
popup the org-agenda view. Now (after a M-x package-list-packages U x)
it does nothing and displays No link found. Is there a way to restore
the old behaviour?
Sorry - I don't know what the version was that had this feature
Hello,
Coleman Gariety writes:
> I agree. However, in specialized fields (linguistics and philosophy, for
> example), single quotation marks are commonly used to refer to technical
> terms or specialized uses of words
>
Hello,
Joseph Lloyd writes:
> I have the following heading:
>
> * Example & Test
>
> When I create the following link to it, I expect it to navigate to the
> heading when I call org-open-at-point (C-c C-o):
> [[Example & Test][Example & Test]]
>
> Instead, calling org-open-at-point offers to
Nicolas,
Thank you for your response.
> When you need that level of precision, smart quotes are not for you.
I agree. However, in specialized fields (linguistics and philosophy, for
example), single quotation marks are commonly used to refer to technical
terms or specialized uses of words
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hello,
Carlos Pita writes:
> I've improved the commit message to better fit org mode conventions
> and also added a note to ORG-NEWS about the new feature. Let me know
> if there still is something I should change or feel free to amend it
> to your liking.
Applied. Thank you!
> One question
Hello,
xristos writes:
> At some point, the optional argument LOCAL was added to org-capture-get:
>
> (org-capture-get PROP LOCAL)
>
> "When LOCAL is set, use the local variable ‘org-capture-current-plist’,
> this is necessary after initialization of the capture process,
> to avoid conflicts
> Arne Babenhauserheide writes:
>
> > In my setup, it deletes footnote [fn:2].
> >
> > Damn, I missed one important part in the ECM: Set
> >
> > org-footnote-section
> >
> > to nil. Does it still leave them untouched?
>
> I still cannot reproduce it.
Then I’ll need to test this in org
At some point, the optional argument LOCAL was added to org-capture-get:
(org-capture-get PROP LOCAL)
"When LOCAL is set, use the local variable ‘org-capture-current-plist’,
this is necessary after initialization of the capture process,
to avoid conflicts with other active capture processes."
Hi Nicolas,
I've improved the commit message to better fit org mode conventions
and also added a note to ORG-NEWS about the new feature. Let me know
if there still is something I should change or feel free to amend it
to your liking.
One question for future patches: is it ok to add a link to the
ghItlhpu' Daniel Borchmann :
> I get (in the *scratch* buffer):
>
> (facep nil) → [face unspecified unspecified unspecified unspecified
> unspecified unspecified unspecified unspecified unspecified unspecified
> unspecified ...]
Seems this an issue with my configuration, not Emacs itself,
ghItlhpu' Nicolas Goaziou :
>> The reason for this seems to be that
>> ‘org-activate-links’ uses the following code to determine which face to
>> use:
>>
>> --8<---cut here---start->8---
>> (pcase (org-link-get-parameter type :face)
>> ((and (pred functionp)
Hello,
Arne Babenhauserheide writes:
> In my setup, it deletes footnote [fn:2].
>
> Damn, I missed one important part in the ECM: Set
>
> org-footnote-section
>
> to nil. Does it still leave them untouched?
I still cannot reproduce it.
> It does not reference between included files, but
Hello,
Daniel Borchmann writes:
> links in Org Mode 9.2 are not highlighted anymore if no :face keyword is
> given in ‘org-link-parameters’.
I cannot reproduce this.
> The reason for this seems to be that
> ‘org-activate-links’ uses the following code to determine which face to
> use:
>
>
Hey,
links in Org Mode 9.2 are not highlighted anymore if no :face keyword is
given in ‘org-link-parameters’. The reason for this seems to be that
‘org-activate-links’ uses the following code to determine which face to
use:
--8<---cut here---start->8---
Hello,
Carlos Pita writes:
> Here is a patch. It removes quite a few LOC.
Thank you.
> Every other previewer has :use-xcolor t. I assume it's safe to simply
> ignore :use-xcolor if it's there except that some user has configured
> a converter that for some reason requires the color command
Hello,
Coleman Gariety writes:
> Also, it occurs to me that one can make use of single quotation marks as
> primary quotes when mentioning a word without using it. Moreover, when
> italics and double quotation marks are also present, the use of single
> quotations as primary is necessary.
>
>
Hello,
I recently upgraded to org 9.2 (release_9.2-4-g284799) and just wanted
to note that I am still seeing this cosmetic issue that Bernt reported.
Josiah
Here is a patch. It removes quite a few LOC.
> I think option 3 is better. Is there any use case left for :use-xcolor?
Every other previewer has :use-xcolor t. I assume it's safe to simply
ignore :use-xcolor if it's there except that some user has configured
a converter that for some reason
Nicolas,
Thank you for your response. I now see that I had misunderstood the
documentation.
Also, it occurs to me that one can make use of single quotation marks as
primary quotes when mentioning a word without using it. Moreover, when
italics and double quotation marks are also present, the use
Nicolas Goaziou writes:
>> here’s a minimal release. Add it into an org-file, then create main.org
>> and sub.org with M-x org-babel-tangle. Finally run the code-block in
>> main.org.
>>
>> #+BEGIN_SRC org :tangle main.org
>> ,#+include: sub.org
>>
>> Here is a footnote[fn:1]
>>
>> run the
Hello,
Carlos Pita writes:
> Considering the above, do you still want me to write a patch for this?
>
> Some options:
>
> 1. Add the above as a remark in the user guide or the wiki.
>
> 2. Add a variant of the dvipng backend, say dvipng-xcolor, as explained.
>
> 3. Remove the dvipng cli color
On 1/1/19, Nicolas Goaziou wrote:
>> stuff you don't need in the agenda, or you have a broken log mode.]
>>
>> but i'm wondering if my emails are reaching the list.
>
> They do.
>
> For the record, I will not try to fix that bug. Someone else may do,
> though.
>
> Regards,
thank you for
Carlos Pita writes:
> 2. If the parser identifies a block how is it in a better position to flag
> it as outdated regarding fontification? Do you mean completely
> circumventing the search based font lock mechanism with its multiline
> property and region extensions? That is, directly setting
Considering the above, do you still want me to write a patch for this?
Some options:
1. Add the above as a remark in the user guide or the wiki.
2. Add a variant of the dvipng backend, say dvipng-xcolor, as explained.
3. Remove the dvipng cli color code and (maybe just deprecate or ignore)
the
3. Or maybe you mean a region extension function that uses the parser to
find out the opposite delimiter of a block?
>
>
> I'd
> rather see work to integrate fontification with the parser.
>
I could take a look at this sometime in the next few months but I'm not
sure what do you mean. In particular:
1. Is the parser doing partial parsings of every inserted/removed character
or line in a more or less complete
Hello,
Samuel Wales writes:
> On 12/22/18, Samuel Wales wrote:
>> at least i /think/ this is a bug.
>
> [what i mean is, as opposed to there already being a fix, or it being
> an intentional feature. i am pretty sure it is a bug: you either have
> stuff you don't need in the agenda, or you
Hello,
Carlos Pita writes:
> Here is a patch on top of latest revision. It just adds an extension
> function while initializing font locking, as documented in [1]. It
> indeed reduces lines of code to some extent by moving the dirty stuff
> out of the fontification function (but I tried to keep
Hello,
David Wen Riccardi-Zhu writes:
> I use the following capture template to store bookmarks:
>
> * %^L :PROPERTIES: :NOTES: %^{NOTES} :END: :LOGBOOK: - Added %U. :END:
>
> It was working fine until I updated my packages today. If I try to use
> the template now, the following is displayed
Hello,
Coleman Gariety writes:
> According to documentation (org-export-with-smart-quotes) should treat
> "pairs of single quotes as secondary quotes." This text:
Only within primary quotes! If there are no primary quotes around, you
don't need a second level of quotation, and single quotes
I use the following capture template to store bookmarks:
* %^L :PROPERTIES: :NOTES: %^{NOTES} :END: :LOGBOOK:
- Added %U.
:END:
It was working fine until I updated my packages today. If I try to
use the template now, the following is displayed in the
minibuffer:
org-capture: Capture
According to documentation (org-export-with-smart-quotes) should treat
"pairs of single quotes as secondary quotes." This text:
'foo'
Should be exported to HTML as:
foo
However, org-mode 9.1.14 exports this text as:
foo
This does not occur when a secondary pair of quotations occurs within a
On 12/22/18, Samuel Wales wrote:
> at least i /think/ this is a bug.
[what i mean is, as opposed to there already being a fix, or it being
an intentional feature. i am pretty sure it is a bug: you either have
stuff you don't need in the agenda, or you have a broken log mode.]
but i'm wondering
Hello,
Arne Babenhauserheide writes:
> here’s a minimal release. Add it into an org-file, then create main.org
> and sub.org with M-x org-babel-tangle. Finally run the code-block in
> main.org.
>
> #+BEGIN_SRC org :tangle main.org
> ,#+include: sub.org
>
> Here is a footnote[fn:1]
>
> run
Hi Nicolas,
Thank you for your answer!
Nicolas Goaziou writes:
>> When a file uses #+include: X.org to structure an org-file and the
>> included files use footnotes defined in the master file, export works
>> without problems, but sorting the footnotes by reference with
>> : C-u M-x
Hello,
Arne Babenhauserheide writes:
> When a file uses #+include: X.org to structure an org-file and the
> included files use footnotes defined in the master file, export works
> without problems, but sorting the footnotes by reference with
> : C-u M-x org-footnote-action s
> removes the
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Hi Nicolas,
Sorry to reply this old thread but...
Would you mind to apply this fix to the maint branch as well?
Thanks in advance.
--
yashi
On Mon, Jul 2, 2018 at 7:32 AM Nicolas Goaziou wrote:
>
> Hello,
>
> 孙振祥 writes:
>
> > the org file like
> > : abc
> > : def
> >
> > and
at least i /think/ this is a bug.
i like to set log mode to show everything. i also go to
previous dates to find out what i did.
however, the skip variables can change log mode.
===
consider org-agenda-skip-scheduled-if-done. showing is
useful for "what was doneified at an unspecified date
Here is a patch on top of latest revision. It just adds an extension
function while initializing font locking, as documented in [1]. It
indeed reduces lines of code to some extent by moving the dirty stuff
out of the fontification function (but I tried to keep the code
formatting of your last
Hi,
I found out that there is already code doing what I proposed but just
when the backend is not dvipng.
If you want to keep using dvipng you can set:
(let ((dvipng (alist-get 'dvipng org-preview-latex-process-alist)))
(plist-put dvipng :image-converter '("dvipng -D %D -T tight -o %O %f"))
>
>
> > Maybe you could rewrite my function in a better way using the
> > precomputed latex regexps and augmenting them with #+BEGIN/END
> > counterparts.
>
> Per above, I'm not really interested in writing yet another workaround
> for something that is going to fail anyway. For the time being, I
Hello,
Carlos Pita writes:
> I still believe that explicitly extending the region is a saner
> approach, it's the documented one at least.
The only sane approach for fontification is to use the parser. Any
solution relying to regexps is bound to fail somewhere, because Org
syntax cannot be
Nicolas, I have modified org-fontify-meta-lines-and-blocks-1 following
your approach:
@@ -5991,6 +5991,13 @@ by a #."
(dc3 (downcase (match-string 3)))
end end1 quoting block-type)
(cond
+ ((and (match-end 4) (equal dc3 "+end"))
+ (save-match-data
+
Also, in the example above, when you change and restore the opening
clause, refontification doesn't happen immediately, you have to
somewhat move the point to retrigger fontification.
> #+END_XXX python
Just #+END_XXX, of course.
401 - 500 of 9192 matches
Mail list logo
