Mekeor Melire writes:
> But it results in empty (nil, I guess) time-stamps being displayed as
> the current time; and non-nil time-stamps being displayed with the
> current hour and minute. What's wrong?
Empty time-stamps will be literally empty: "" (that is: empty string).
(if "" 1 2) will
Roger Mason writes:
> File is missing: Cannot open load file, No such file or directory, org
>
> This is the backtrace from emacs --debug-init:
>
> Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such
> file or directory" "org")
> require(org)
>
>
Stefan Kangas writes:
> Please see the attached.
Thanks!
Applied onto main via 41e19f1d7.
Best,
Ihor
Aimé Bertrand writes:
> New patch file attached.
Thanks!
Applied onto master via aeb504f6.
> + It's also available in [[https://melpa.org/#/org-mac-link][MELPA]].
Is there any reason why you did not publish on non-GNU ELPA?
Best,
Ihor
Richard Stallman writes:
> I agree that links to liberapay might someday work without the donor's
> running nonfree software. But that is not likely to occur this year,
> and for it to occur in this decade is a long shot.
>
> So please don't put links to liberapay into GNU package web pages.
Samuel Wales writes:
> idk about others, but as a luddite follower of bugfix/maint, if
> poissible and not too annoying to do, i would be interested in
> knowing, at the email subject header level, that the upcoming
> bugfix/maint release [state org version number] will not support <=
> [state
Bhavin Gandhi writes:
> Currently, when we call `org-auto-repeat-maybe', it adds
> `org-add-log-note' to post-command-hook using `org-add-log-setup'. As
> soon as we reach the question about 10 repeater intervals (the call to
> `y-or-n-p' from `org-auto-repeat-maybe'), the post-command-hook gets
Juan Manuel Macías writes:
>> actual notes below:
>
> Awesome notes. Hats off to such a detailed capture (reminds me to give
> my poor org-capture templates some more love one day :-))
This capture template is public: https://github.com/yantar92/org-capture-ref
Best,
Ihor
Max Nikulin writes:
> On 30/06/2022 18:19, Stefan Kangas wrote:
>> The attached patch deletes some Emacs 24 compat code. Org mode
>> supports Emacs 26 or later, according to:
>> https://orgmode.org/worg/org-maintenance.html#emacs-compatibility
>
> I have no particular opinion to which degree
Juan Manuel Macías writes:
> Sorry for the slight offtopic. I'd like to be able to graphically
> convert (from a src block) a Lisp expression to a tree diagram, similar
> to trees used in (human) syntax and grammar, especially generative
> grammar (this is a web app for generating such trees:
>
Ihor Radchenko writes:
>> ;;; Integration with and fixes for other packages
>> diff --git a/lisp/org-fold-core.el b/lisp/org-fold-core.el
>> index 88072852d..287686c01 100644
>> --- a/lisp/org-fold-core.el
>> +++ b/lisp/org-fold-core.el
>> ...
>> +(def
Stefan Kangas writes:
> The attached patch deletes some Emacs 24 compat code. Org mode
> supports Emacs 26 or later, according to:
> https://orgmode.org/worg/org-maintenance.html#emacs-compatibility
Thanks! I have some comments.
> ;;; Integration with and fixes for other packages
> diff
Tim Cross writes:
>> The latest manual has the correct link. I assume that you have fixed it.
>> I guess that some of your questions do no apply anymore.
>
> Correct. I made some minimal changes to address the worst failing
> aspects. However, a lot more work to do to really clean things up.
>
Robert Pluim writes:
> >> Occasional committers would probably not read org-maintenance.org, and
> >> those are the people this section is aimed at, I think. Plus itʼs the
> >> kind of thing you need to catch early: once the commit has been pushed
> >> itʼs too late.
>
>
"Updating the list of hooks/commands/options on Worg" section of
https://orgmode.org/worg/org-maintenance.html is referring to mk/eldo.el
which does not exist.
>From git history, eldo.el is now located inside worg/code/eldo.el
The other linked file - https://orgmode.org/worg/doc.html is
Michael Maurer writes:
> Here's how it looks vs. how I want it to look https://imgur.com/a/5YfTeZh
See org-agenda-todo-keyword-format.
Best,
Ihor
Gerardo Moro writes:
> I have been trying for over a year to change the output plot size when
> using Orgmode SRC blocks with R. I have tried both using orgmode settings
> and R settings.
Have you tried :with and :height header arguments?
> I have a table from which I take some values.
It
"T.V Raman" writes:
> 1. Accessibility as word used in isolation has now become mostly
>meaningless, to be concrete one has to ask "Accessibility to whom"?
>
> 2. So in the following, everything I say is with respect to users with
>visual impairments.
This is exactly the perspective I
Aimé Bertrand writes:
> org-mac-link was removed from org-contrib with
> https://git.sr.ht/~bzg/org-contrib/commit/c6aef31ccfc7c4418c3b51e98f7c3bd8e255f5e6.
>
> This is a patch (attached) for Worg to reflect the changes.
Thanks for the patch!
> --- a/org-contrib/index.org
> +++
Stefan Kangas writes:
> Ihor Radchenko writes:
>
>> Applied onto main via a722f6f8e with amendment to the commit message.
>
> It seems like i bungled the patch: two typos are fixed in the attached.
> Thanks.
I swear I did check for this... Still missed.
Applied onto mai
Stefan Kangas writes:
> The attached patch improves the look of the agenda time grid and
> separator line on graphical displays. It was inspired by
> org-modern.el by Daniel Mendler.
Applied onto main via 998a0aacd.
Best,
Ihor
Tim Cross writes:
> in my attempt to fix up some issues on the Worg site, I'm finding there
> is considerably more things broken than I initially realised. One of
> these things is 'the library of babel".
>
> There is a link to the library-of-babel.org file on worg from within the
> Emacs
Stefan Kangas writes:
>> I am wondering if this is meaningful considering that Org is not always
>> distributed together with Emacs. Will this :version tag make any sense
>> for people using the newest Org with older Emacs versions?
>
> I think it won't really, but that's okay. Also, this is
Stefan Kangas writes:
> Ihor Radchenko writes:
>
>> > 2. Delete the file from org-mode.git
>> > ...
>> > What do you think?
>>
>> Sounds good to me.
>
> Patch attached.
Applied onto main via ea05f4343.
I removed the dot after the commit message.
Best,
Ihor
Robert Pluim writes:
>>>>>> On Mon, 27 Jun 2022 17:53:30 +0800, Ihor Radchenko
>>>>>> said:
>
> Ihor> Robert Pluim writes:
> >> diff --git a/org-contribute.org b/org-contribute.org
>
> Ihor> Maybe add the d
Matt Huszagh writes:
> Modifications made and split into two patches. Let me know if any
> remaining issues.
> From 7af7ad3990410ca388c841e045ec66ce694b404a Mon Sep 17 00:00:00 2001
> From: Matt Huszagh
> Date: Mon, 27 Jun 2022 20:42:27 -0700
> Subject: [PATCH 2/2] ob-core.el: Improve
Stefan Kangas writes:
> The attached patch improves the look of the agenda time grid and
> separator line on graphical displays. It was inspired by
> org-modern.el by Daniel Mendler.
Thanks! Looks good.
>:group 'org-agenda
> + :version "29.1"
> ...
> - :version "24.1"
> + :version
Stefan Kangas writes:
> Note that the "." is on the next line (you can't see it in the patch though).
>
>> Thanks, I'll update the patch.
>
> Please see the attached.
Thanks!
Applied onto main via a722f6f8e with amendment to the commit message.
I have added quoting to the variable name:
Daniel Ortmann writes:
> ... I rebuild at least once per day.
> My current org-mode version is:
> Org mode version 9.5.4 (release_9.5.4-596-gaa5bc2 @
> /home/dortmann/src/git-org-mode/lisp/)
>
> A bit more information may help?
>
> * 1.2MB org-mode file
> * received a stubborn parse error
Matt Huszagh writes:
> Ihor Radchenko writes:
>
>> I think that it will be better if you use
>> org-latex--caption/label-string instead. It will take care about short
>> captions as well.
>
> Changing this to (?c . ,caption-str) yields for the original example
Stefan Kangas writes:
> org-install.el has been obsolete for more than 10 years.
> ...
> 2. Delete the file from org-mode.git
> ...
> What do you think?
Sounds good to me.
Best,
Ihor
Cristi Constantin writes:
> Than you for the response! I tried the fix you suggested, but I still
> see this:
I just pushed a commit that should hopefully fix this problem. Please
update Org and let me know if you keep seeing the warning.
Best,
Ihor
Daniel Ortmann writes:
> Hey there,
> I have a 1.2+ MB org-mode file and have been getting the following
> message for a week or two. I have cleaned up content by archiving older
> content and have run org-lint to cleanup some syntax issues ...
>
> How to debug this type of issue?
Thanks for
"Samuel Banya" writes:
> 8. I then used C-c C-c, and received the following example output:
> ```
> * tes
> :LOGBOOK:
> - Note taken on [2022-06-27 Mon 22:38] \\
> Adding note with org-log-into-drawer enabled
> :END:
> t
> ```
>
> Let me know if this is the desired output in that respect, or
Tim Cross writes:
> Given that the FSF has a link to PayPal on their donations page , I
> think we can do the same for the org project. All that is required is
> that we do like the FSF does and put a bit of text beside it stating
> "Not recommended - requires nonfree Javascript".
> I also
Michael Powe writes:
> Anyone completely serious about a refusal to use nonfree tools for
> making donations will send a check in the mail, literally.
Would providing something like
"Contact us via email if you prefer to make a donation using alternative
mechanism"
help if we add such
"Aaron L. Zeng" writes:
> ---
> lisp/org-agenda.el | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks!
Applied onto main via ac7b8f9d2 with amendments to the commit message.
I have added TINYCHANGE cookie a more detailed changelog entry.
Best,
Ihor
Gregor Zattler writes:
>> Are you seeing the same warning? ("Invalid search bound ...")
>
> no, it's
>
> Cached element is incorrect in xxx.org. (Cache tic up to date: "yes")
> Resetting.
>
> The element is: "(headline (:raw-value
> The real element is: "(fixed-width (:begin...
> Cache
Richard Stallman writes:
> GNU packages should not steer people towards running nonfree software.
> As a consequence, they should not suggest people donate using payment services
> that _require_ the donor to run a nonfree program.
AFAIU, there are no nonfree payment services, except some
"Samuel Banya" writes:
> I checked 'org.el' which has the related 'org-add-note' function present.
>
> This appears to call the 'org-add-log-setup' function, and passes the 'note'
> argument to it.
>
> I then took a look at the 'org-add-log-setup' function.
>
> From the bug's nature itself, it
Gregor Zattler writes:
> Hello org-mode devs, Ihor,
>
> today, when opening several org files for my agenda, I got a
>
> Warning (org-element-cache): ...
Thanks for reporting!
This is probably similar to
https://list.orgmode.org/87a69ypk1m.fsf@localhost/T/#t
Are you seeing the same warning?
Ivar Fredholm writes:
> I believe the two could be unified if we expand the functionality of
> the async filter to look for 'exception' tags. Then each language
> implementation must only put the org-babel src block in a try-except
> type construction and put the error message into the except
Robert Pluim writes:
> diff --git a/org-contribute.org b/org-contribute.org
Maybe add the details to org-maintenance.org instead?
This is more of a technical detail needed for maintainers, not for the
committers.
> +1. Command line: src_sh{git commit --author='First Last
> '}
I think we
Stefan Kangas writes:
> Subject: [PATCH 1/2] Move appendix on performance in manual to agenda chapter
>
> * doc/org-manual.org (Speeding Up Your Agendas): Move section to
> chapter "Agenda Views".
Does it have to be inside the main chapters of the manual?
I really hope that users do not
Cristi Constantin writes:
> Than you for the response! I tried the fix you suggested, but I still
> see this:
>
> Warning (org-element-cache): org-element--cache: Org parser error in
> 2022-log.org::179869. Resetting.
> The error was: (error "Invalid search bound (wrong side of point)")
"Samuel Banya" writes:
> Ihor, can you take a look at the .mkv video I attached of my test and let me
> know what you did to be able to reproduce this because I'm not observing any
> errors on my machine.
You misunderstood the email formatting.
#+begin_example
* test
#+end_example
actually
Fabio Natali writes:
> Incidentally and FWIW, this is a bit counter-intuitive to me. I'd have
> expected everything withing a comment or literal block to be treated as
> content until the ending statement, =#+end_comment= or =#+end_src=
> respectively. I suppose that this makes sense in the
Let me take a freedom to add T.V Raman to the discussion. This thread
might be of interest for him and he probably knows a lot more about
accessibility options.
This thread starts at
https://list.orgmode.org/87v8sn3obd@gmail.com/T/#u
Juan Manuel Macías writes:
> Tim Cross writes:
>
>> As I
Raymond John Abayan writes:
> I have the following error and coudn't seem to find a solution online.
> Warning (org-element-cache): org-element--cache: Org parser error in *Org Src
> init.org[ elisp ]*::115. Resetting.
> The error was: (error "rx ‘**’ range error")
> Backtrace:
> nil
Thanks
Ivar Fredholm writes:
> Specifically for ob-python, if an exception happens before we can print the
> 'end' token used by async-filter, there will be no output or indication of an
> error.
Could you please provide steps to reproduce, detail what you expected
and what you actually get?
See
Allen Li writes:
> Attached
Thanks!
Applied onto main via 711ada5ac.
I changed the patch slightly adding
;; FIXME: Add tests for all other allowed prefix arguments.
line to the test.
Best,
Ihor
Ihor Radchenko writes:
> Applied onto main via 15068ce30.
Forgot to mention that I amended the commit message adding the "." at
the end of the sentence and using the `symbol' quoting style for
symbols.
Best,
Ihor
Rudolf Adamkovič writes:
> Please, see the attached patch.
> ...
> Subject: [PATCH] Fix incorrectly documented MathJax options
>
> * lisp/org/ox-html.el (org-html-mathjax-options): Fix some incorrect
> choices for 'indent' and 'autonumber' in the docstring
Thanks!
Applied onto main via
Stefan Kangas writes:
> It seems like the `org-agenda-custom-commands' docstring had some
> missing and incorrect information. Please see the attached patch that
> should improve the situation slightly.
Thanks for this patch and for the other stylistic/docstring fixes! It is
great that someone
Allen Li writes:
>> Would you also be interested to write a test checking org-todo ARGS?
>>
>
> Attached
Thanks! However, it is unclear what this test is checking for.
> +(ert-deftest test-org/org-todo-prefix ()
> + "Test `org-todo' prefix arg behavior."
> + ;; -1 prefix arg should cancel
Arthur Miller writes:
> Ihor Radchenko writes:
>
>> Arthur Miller writes:
>>
>>> I have reworked a bit org-capture, but I haven't yet worked on org-agenda
>>> restrictions and other details.
>>
>> I do not think that you need to prioritize re
Ivar Fredholm writes:
> At this point, Babel calls org-babel-execute:python, which decides, based on
> the 'session' header, whether or not to call python3 tmp_code.py or to feed
> each line in tmp_code.py into the session interpreter. What I am wondering is
> if we could replace the code for
"Fraga, Eric" writes:
> On Tuesday, 21 Jun 2022 at 10:01, M. ‘quintus’ Gülker wrote:
>> I am working on a presentation for a conference (using org-mode and its
>> beamer export) and want to exchange the entire background for a specific
>> frame with an image. This is possible with Beamer, see
>
Tim Cross writes:
> Sadly, org isn't great from an accessibility perspective. This is
> something I would like to see improved, but it is a huge and complex
> task. There are some 'easy' winds we could try. For example, org still
> defaults to using the and tags instead of
> and . Likewise,
Ivar Fredholm writes:
> A session-less block can be executed by starting a session with a special
> name (say "*none") which always gets killed after block execution is
> completed. For interpreter-less languages, we could use the shell as an
> interpreter (for instance, if we wanted to
Stefan Kangas writes:
> Ihor Radchenko writes:
>
>> Thanks! So, Emacs now advises to use "website" and "URL:", right?
>> Mentioning this fact, and the relevant commit would improve the commit
>> message. (that is: please update the commit messa
Daniel Fleischer writes:
> Thank you very much for the patch. It was merged to master in 4a0d951c.
> Also, you were added to the orgmode contributes at
> https://orgmode.org/worg/contributors.html.
>
> Thanks for the contribution.
This commit triggers
In org-latex--align-string-tabbing:
Fabio Natali writes:
> Now consider a slight variation where "Hello world" is formatted as a
> Org heading. The 'org-babel-goto-named-src-block' function is no longer
> able to identify the text block. Executing the Emacs Lisp block results
> in the error message below.
>
> #+name: bar
>
Max Nikulin writes:
> On 25/06/2022 17:39, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> The following example is somewhat contrived. Try to set different
>>> options (width or e.g. angle) for several inline images. It applies to
>>> LaTeX as wel
Max Nikulin writes:
> Certainly it is possible to document that attributes are mostly useful
> for image links when they are block-level elements rather than inline
> objects. Caveats of trying to use attributes for inline objects should
> be clearly stated to avoid false expectation of
Arthur Miller writes:
> I have reworked a bit org-capture, but I haven't yet worked on org-agenda
> restrictions and other details.
I do not think that you need to prioritize re-creating
org-capture/org-agenda/etc The main point is making sure that org-select
provides the required
Rudolf Adamkovič writes:
> After thinking about this for a while, I realized I do not know when I
> will have the time to implement the proposed improvements. So I wonder,
> should we merge what we have, with the feature disabled by default using
> the existing customization variable? That
Stefan Kangas writes:
> In "(org) Agenda Dispatcher", we have the following incorrect part:
>
> A prefix argument can be used
> to specify the number of context lines for each match, default is
> @enumerate
> @item
> @end enumerate
Thanks!
Applied onto main via db3870bfc
Alessandro Bertulli writes:
> I noticed that, when using eshell, sometimes Emacs inserts some non
> requested tabs. For instance, let's say I have:
> ...
Note that you are writing to the mailing list dedicate to Org mode. Your
issue does not appear relevant. You may have better luck asking
Colin Baxter writes:
> > I do not see much improvement using your variant as well. Also,
> > note that, for example, Elisp manual is full of constructs like
> > what we are discussing.
>
> The line could be removed?
Then we will lose an important information.
I personally do not
Max Nikulin writes:
> Org Manual in info "(org) Links in HTML export"
> https://orgmode.org/manual/Links-in-HTML-export.html has the following
> example:
>
>> Org files can also have special directives to the HTML export
>> back-end. For example, by using ‘#+ATTR_HTML’ lines to specify new
>>
Ihor Radchenko writes:
> A more efficient way could be introducing a new customization similar to
> org-cycle-hide-block-startup. Say, it can be
> org-cycle-hide-drawer-startup. See the attached patch.
Applied onto main via bcfed0f34.
Best,
Ihor
em...@vergauwen.me writes:
> Hi Robert,
> I used the instructions provide on
> https://orgmode.org/worg/org-contribute.html#first-patch.
> For me, it was a first too, send a patch via email. Can I
> prevent these issues in the future or use a different method
> to send my patches?
I think we
Ypo writes:
> elisp-bug-hunter sadly seems to have some bug, so I can't use it
> interactively anymore.
>
> https://github.com/Malabarba/elisp-bug-hunter/issues/29
>
> You are right, about the .org files though.
I haven't seen any issues using M-x bug-hunter-init-file.
I follow the procedure
DEBRY.Edouard writes:
> if I perform Alt-leftarrow on mmd, this element is shift on the left
> but then the whole list is turned into :
> - first
>- ssdsd
>- mmd
> - second
>
> Is there a way to avoid that ?
I am unable to reproduce on the latest main and bugfix.
Best,
Ihor
Ypo writes:
> Yes, I tried your assertion for bug-hunter, but it didn't work.
>
> (unless (eq 'universal-argument (keymap-lookup global-map "C-u"))
> (error "C-u has been redefined"))
You can also bisect interactively instead of using assertion.
Note that your assertion is not expected
David Lukeš writes:
> Thanks! OK, will do, thanks for letting me know.
Note that FSF should reply within 5 working days. If they do not, feel
free to ask here for further assistance.
Best,
Ihor
Colin Baxter writes:
> I think that this potentially confusing to someone unfamiliar in the
> format of an info file. I had thought of suggesting the line be changed
> to "The next sections have further details." That suggestion however is
> no better that what is in place already.
I do not see
Colin Baxter writes:
> M-: produces "/home//git/org-mode/doc/"
>
> Is it not that the org version has indeed further sections beneath, but
> these are not visible on the single info page?
I feel that I am confused.
Can you elaborate what exactly you expected and what you see instead?
Best,
Robert Pluim writes:
> I was just about to start implementing calendar navigation commands
> for org-read-date, except that they all already exist :-). Theyʼre
> just not documented in the docstring, only in the manual. Patch
> adding a cross-reference attached.
Thanks!
Applied onto main via
David Lukes writes:
> * lisp/oc-basic.el (org-cite-basic--parse-json): Make sure year
> extracted from date-parts is returned as string. Raise error if
> original type other than number or string.
Thanks!
Applied onto bugfix via 05626952b.
Note that the total LOC of your contributions is
Asilata Bapat writes:
> Ihor Radchenko writes:
>> Could you please provide a detailed reproducer?
>
> Sure. I have attached the files "mwe-data.org" and "mwe-export.org".
>
> To reproduce, save both files in the same directory. Then open
> mw
Bruno Barbier writes:
> From what I understand, the function 'org-babel-sh-evaluate' relies on
> 'call-process'; and that function ignores file name handlers; as TRAMP
> relies on those file name handlers, it just cannot do the right thing.
>
> Using 'process-file' instead works for me.
>
> See
Cristi Constantin writes:
> I'm just editing my normal org log files and I started seeing the errors
> above after I upgraded to latest org-mode.
> I think I didn't upgrade for a month, so this bug is pretty new.
> It doesn't seem to do anything weird, but I see this traceback a few
> times a
Uwe Brauer writes:
>> I recommend to hide such table inside drawer and set
>> org-export-with-drawers appropriately.
>
> Thanks, any type of drawer in particular?
Feel free to consult the docstring of org-export-with-drawers
Best,
Ihor
Bastien writes:
>> https://todo.sr.ht/~emacs/emacs/2 could be somewhat useful.
>
> Yes, somewhat: but I'm not yet clear on the steps to set up a mirror.
>
> If anyone can guide me from A to Z, I'd be glad.
The discussion mentions some cron job.
Quick googling yielded
Bastien writes:
>> There is such a SourceHut project: https://sr.ht/~bzg/orgmode/
>
> The sr.ht project is now on https://sr.ht/~bzg/org/ and lists all
> relevant repositories, including a mirror of the official org-mode
> repository at https://git.sr.ht/~bzg/org-mode.
I just found some
Lourens van der Vliet writes:
> Org mode version 9.6 (9.6-??-971eb68 @
> c:/Users/xpar/.emacs.d/.local/straight/build-27.2/org/)
> I performed this week a sync with doom emacs. This the last version.
Nope. 971eb68 is a 3 month old commit.
Looking at
Uwe Brauer writes:
> I have a org-table in a comment environment, since I don't want to export it.
>
> However you can I edit the table using org-table commands, orgtbl-mode
> is ignored, so what shall I do?
>
> That seems as a stupid question, but I can't find its obvious answer.
Everything
Tor Kringeland writes:
> Most of the text will then be hidden, with "test" showing as a link, as
> expected. However if I remove the last ], the link highlighting
> disappears and only "test" is shown like regular text (/i.e./ instead of
> "[[123][test]" as would be expected). If I insert a
Colin Baxter writes:
> The latest org-mode info has a section entitled: "13.10.2 LaTeX specific
> export settings". At the foot of that Section is the line: "The
> following sections have further details." There is nothing following.
I do have section 13.10.3 and the subsequent sections on my
Tor Kringeland writes:
> Ihor Radchenko writes:
>
>> Aha. Not saving is an important piece of information.
>> (said the person with compulsive saving syndrome)
>
> Thanks! This fixes the bug (which was present in both Org 9.5 and 9.6)
> for me. However, my original
Uwe Brauer writes:
>> See org-html-with-latex. We use mathjax syntax for LaTeX export by
>> default
>
> I see, but that means, the exported wiki cannot be used say for
> wikipedia since it uses mediawiki syntax for math.
>
> Does anybody knows about a 3rd party package providing support for
Max Nikulin writes:
> Consider the following case. A user has 2 virtual desktops dedicated to
> rather independent tasks and an Emacs frame on each desktop. On desktop
> 1 she opens help for some function with aim to evaluate if it is
> appropriate for some particular purpose. Next she has to
Jack Kamm writes:
> Therefore, I am canceling the help request (or rather, attempting to
> cancel it with Woof -- this is my first time using Woof like this, so
> apologies in advance if it doesn't work).
Thanks for taking care of this!
> This help request is old, and also it was never clear
David Lukeš writes:
>> Would you mind creating a patch and possibly supplying a test
>> that will make sure that the example file and similar are correctly
>> parsed?
>
> I'm attaching a patch (just the patch for now, no commit message), let
> me know what you think, in particular the error
Uwe Brauer writes:
> The following line
>
>
> torus $\mathbb T^3$ in the Sobolev spaces $H^m(\mathbb T^3)$.
>
> Is translated to
>
> torus \(\mathbb T^3\) in the Sobolev spaces \(H^m(\mathbb T^3)\)
>
> Instead of
>
> torus \mathbb T^3 in the Sobolev spaces H^m(\mathbb
> T^3)
>
> Is this a
"Samuel Banya" writes:
> Confirmed with 'emacs -Q -L ./lisp/ -l org' on latest version of Org.
>
> @Ihor, can you help push me in the right direction in terms of where in the
> codebase this issue might lie, so that I can examine the related section
> myself, and also bug a related maintainer
Tor Kringeland writes:
> Ihor Radchenko writes:
>
>> Can you reproduce the problem starting from emacs -Q?
>
> I did. The bug only occurs if there is no newline at the end. So for
> example if you open a new buffer and don't save it, the bug should
> occur.
Aha. No
Tor Kringeland writes:
> Consider the following buffer
>
> #+begin_example
> * test
> #+end_example
>
> without a newline at the end. Calling `org-add-note' will result in an
> error and the note being placed /before/ the heading.
I am unable to reproduce.
Can you reproduce the problem
1 - 100 of 1861 matches
Mail list logo