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.
Hi John!
I was using org-ref some time ago, but it seemed to get emacs slower, in my low
resources PC.
Would you give me some tips to make org-ref lighter?
Best regards
27 ago 2023 2:33:05 John Kitchin :
> You can see how these work in org-ref in this video:
>
Ihor Radchenko writes:
> In other words, it is not the section itself, but other
> headline/inlinetask features, like todo keywords, tags, planning. Right?
No, it is the section itself (or the concept of "section", with its toys
in Org, of course) that is important to me in this case. I am not
On Sat, Aug 26, 2023 at 05:31:46PM +, Juan Manuel Macías wrote:
> Ihor Radchenko writes:
>
> *** TODO anonsec :tag:
> Content that has neither a title nor a section number.
> *** END
>
> and a construction that for the purposes of parceling out the text
Juan Manuel Macías writes:
>> Why not simply
>>
>> #+begin_anonsection
>> ...
>> #+end_anonsection
>>
>> ?
> ... The problem is the LaTeX side. Since there is no
> support for anonymous sections in LaTeX (I seem to remember that some
> special class like Koma had some command to introduce
Ihor Radchenko writes:
> Why not simply
>
> #+begin_anonsection
> ...
> #+end_anonsection
>
> ?
Because with an inlinetask I can have something like this:
*** TODO anonsec :tag:
Content that has neither a title nor a section number.
*** END
and a
I would like to know what do you use for acronyms, glossaries, etc for
using inside org-mode? Not for exportation, just to use them inside Emacs.
Maybe radio links, or the package org-glossary? org-ref?
Best regards
Juan Manuel Macías writes:
>> Do you mean section in LaTeX sense or in Org sense?
>
> In Org sense, I think. If an author adds an 'anonymous' break (through
> some customary symbol) and continues writing, the content that follows
> belongs (for Org) to the current section. By using an
Jack Kamm writes:
>>FAILED 376/1256 test-ob-python/session-multiline (0.011955 sec) at
>> ../lisp/test-ob-python.el:105
>
> Hmmm. Do you have an idea of how long this has been happening, and how
> frequently it breaks?
For months.
> My first suspicion is the large ob-python commit I
Edgar Lux writes:
> 9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
Did you see a new Emacs instance at this point?
> 10. M-x switch-to-buffer RET /tmp/bug.org RET
> 11. Move point to "t = 0" line
> 12. C-c C-x C-l (2x)
>
> I see the warning.
>
> After step 10, I removed the files
Henrik Frisk writes:
>> Is lilypond library is loaded when you open Org file?
>> What happens if you run C-c ' on an src-block?
>>
>
> That works fine, code is syntax highlighted.
Hmm. Did you customize `org-src-fontify-natively'?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn
Margaret Patterson writes:
> Thanks! Yes that seems to fix my problem.
Fixed, on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7c929e9d8
> I failed to apply the patch (perhaps because the file is in a different
> place, /lisp/org/ instead of /lisp/ ) however making
Ihor Radchenko writes:
> Hi,
>
> We have fairly regular CI test failures for one of the ob-python tests.
> The test does not fail _every_ time, but I keep seeing the problem in
> various Emacs versions, including Emacs 29.
>
> Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
>
> In
On Aug 23, 2023 at 9:56 AM, Ihor Radchenko
> 1. Save the equation to file /tmp/bug.org
> 2. Save your `setq' snippet to /tmp/bug.el
> 3. cd /path/to/org/repo
> 4. make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
> 5. Move point to "t = 0" line
> 6. C-c C-x C-l (2x)
> 7. The preview appears and
Thanks! Yes that seems to fix my problem.
I failed to apply the patch (perhaps because the file is in a different
place, /lisp/org/ instead of /lisp/ ) however making that change
manually and rebuilding fixed the problem.
For future reference is there a resource that explains how to apply
Ihor Radchenko writes:
> Juan Manuel Macías writes:
>> I think that would not be expected, since an anonymous section is just a
>> break in the text that has neither a title nor a section number.
>> ... Anonymous breaks using asterisks or other symbols is usually the applied
>> remedy. The
Den lör 26 aug. 2023 kl 14:27 skrev Ihor Radchenko :
> Henrik Frisk writes:
>
> > So I changed to the main branch of
> >
> > git://git.savannah.gnu.org/emacs/org-mode.git
> >
> > and the new features you added to ob-lilypond is working (much
> > appreciated) but I still don' have syntax
On 2023-08-26 14:22, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> #+begin_example
>> boss\-prio="C"
>> boss\:prio="C"
>> boss\\prio="C"
>> #+end_example
>
> Looks good to me.
Implemented in the next version of the patch, please check.
From 11dc3ac4ff060f1ffb9dae7b35eabe526bbbc572 Mon Sep
Hi,
We have fairly regular CI test failures for one of the ob-python tests.
The test does not fail _every_ time, but I keep seeing the problem in
various Emacs versions, including Emacs 29.
Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
In the test the result somehow includes
Juan Manuel Macías writes:
>>
>> May they contain sub-sections?
>
> I think that would not be expected, since an anonymous section is just a
> break in the text that has neither a title nor a section number.
> ... Anonymous breaks using asterisks or other symbols is usually the applied
> remedy.
"Fraga, Eric" writes:
>> My personal use case is when using Org for authoring long texts.
>> I often leave inline tasks around the specific paragraph I need to
>> revise in future:
>
> For completeness, I will add that I do the same but using drawers at the
> point where I want to note a task,
Henrik Frisk writes:
> So I changed to the main branch of
>
> git://git.savannah.gnu.org/emacs/org-mode.git
>
> and the new features you added to ob-lilypond is working (much
> appreciated) but I still don' have syntax highlight in source blocks
> though it works fine in lilypond-mode.
Is
Den ons 23 aug. 2023 kl 08:04 skrev Henrik Frisk :
>
>
> On Tue, Aug 22, 2023, 6:17 PM Ihor Radchenko wrote:
>
>> Henrik Frisk writes:
>>
>> > So I grabbed the file ob-lilypond from another inactive install of Emacs
>> > 29.1 and linked to it in my init file. Everythin appears to work fine
>> >
Jens Schmidt writes:
>> That's partially what I meant.
>> It would help to provide a simpler example first.
>
> How about a series of simpler examples then, like this:
>
> #+begin_example
> boss\-prio="C"
> boss\:prio="C"
> boss\\prio="C"
> #+end_example
Looks good to me.
--
Ihor Radchenko //
On 2023-08-26 14:00, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> On 2023-08-26 12:16, Ihor Radchenko wrote:
>>> This actually feels rather cubersome.
>>
>> [...] I can
>> provide a simpler example in the manual, but that's probably not
>> what you meant :-)
>
> That's partially what I
Jens Schmidt writes:
> On 2023-08-26 12:16, Ihor Radchenko wrote:
>> Jens Schmidt writes:
>>> #+begin_example
>>> -+-long-and-twisted-property-name-="foo"
>>> +\-long\=and\\twisted\:property\.name\*="foo"
>>> #+end_example
>>
>> This actually feels rather cubersome.
>
> That particular
On 2023-08-26 12:16, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> #+begin_example
>> -+-long-and-twisted-property-name-="foo"
>> +\-long\=and\\twisted\:property\.name\*="foo"
>> #+end_example
>
> This actually feels rather cubersome.
That particular example looks awkward, but pls don't
Ihor Radchenko writes:
>> ... They
>> behave like a true section, except that they are not headed by titles or
>> level numbers.
>
> May they contain sub-sections?
I think that would not be expected, since an anonymous section is just a
break in the text that has neither a title nor a section
Juan Manuel Macías writes:
> I think inlinetasks may also have a use for those sections that are not
> "nested". In typography they are usually called "anonymous sections" and
> they are separated by some symbol (asterisks, dinkus[1], etc.).
This is a very interesting idea. Thanks for sharing!
Jens Schmidt writes:
>> IOW, backslash quotes everything except whitespace, which by definition
>> cannot be part of a property name.
>>
>> Will start on this, but with tests and documentation this might take
>> some time.
>
> Here comes a first patch ... please check.
Thanks!
>
On Wednesday, 23 Aug 2023 at 09:33, Ihor Radchenko wrote:
>> "Fraga, Eric" writes:
>>
>>> I'll chime in regarding inlinetasks: I used to use these *a lot*
>>> but I
>>> found that drawers do what I needed in almost all cases very
>>> effectively (for my use cases).
>
> My personal use case is
31 matches
Mail list logo
