On Wed, Oct 25, 2023 at 5:10 AM Ihor Radchenko wrote:
> [ Adding Org ML back to CC ]
>
> George Kettleborough writes:
>
> > I really struggled to come up with a minimal example for this as the
> > behaviour seemed truly bizarre!
> >
> > The best I have is my blog:
> >
> > To build it (ie.
any body in the subtrees, I saw these empty
code blocks), which is not present in the Org source.
If I delete the "* Post 2" line, that empty code block is not exported (as
expected).
Org mode version 9.6.1 (release_9.6.1-116-g07c63d).
--
Kaushal Modi
On Wed, Jan 11, 2023 at 10:50 AM Bastien wrote:
> Ihor Radchenko writes:
>
> > +1
>
> Done, thanks.
>
> Kaushal, it should appear on GNU ELPA in a few hours.
>
Wow, thanks a lot for this prompt action! This will help get the Github
Actions CI status back in green state.. soon :).
> Ihor,
time.
I believe that for Elpa, the only way to update the version is to update
the version in the package's comment header.
--
Kaushal Modi
On Tue, Dec 13, 2022 at 3:51 PM Kaushal Modi wrote:
> On Tue, Dec 13, 2022 at 3:52 AM Ihor Radchenko
> wrote:
>
>> Kaushal Modi writes
On Thu, Dec 15, 2022, 4:32 AM Ihor Radchenko wrote:
> Johan Bolmsjö writes:
>
> > #+caption: Caption 1
> > #+begin_src
> > foo bar baz
> > #+end_src
>
> There is an inconsistency here between Org parser and
> https://orgmode.org/worg/org-syntax.html + manual.
>
> The actual parser does allow
On Wed, Dec 14, 2022, 4:44 PM Johan Bolmsjö
wrote:
> ** Description
>
> The caption "Caption 1" is not exported by ox-html in the following
> source block.
>
> #+caption: Caption 1
> #+begin_src
> foo bar baz
> #+end_src
>
The begin_src block always requires a "language" as far as I know. If
On Tue, Dec 13, 2022 at 3:52 AM Ihor Radchenko wrote:
> Kaushal Modi writes:
>
> > Since Org 9.6, I am seeing that the numbering of tables (and other
> elements
> > like figures) resets to 1 and stays so, thought I cannot see a pattern of
> > why that happens.
&g
--
abcdefgh ijklmnop qrstuvwx
Table 1: Should be Table 4
=
--
Kaushal Modi
Hi Alejandro,
Thanks for reporting this issue. I was seeing the same issue and I wasn't
sure if this issue was in org-mode or the ox-hugo package. It was on my
to-debug list.
Ihor: Thank you for the quick response and fix!
On Sat, Dec 10, 2022, 4:47 AM Ihor Radchenko wrote:
> Alejandro Pérez
On Fri, Oct 28, 2022, 4:25 PM Marcin Borkowski wrote:
> What is the "official" version? I found at least two spelling on
> orgmode.org...
>
> TIA,
>
Here's my personal take on that topic:
https://scripter.co/how-do-i-write-org-mode/
>
On Sun, Oct 16, 2022 at 2:04 AM Bastien wrote:
> Hi all,
>
> thanks to joint efforts by Christian Köstlin and Ihor, we are running
> the Org test suite from the Org main branch against Emacs 26, 27, 28.
>
It's great to hear this. Thank you, Christian and Ihor!
I'd like to join.
--
Kaushal Modi
On Thu, Oct 6, 2022 at 9:24 AM Russell Adams
wrote:
>
> Would there be any interest in a monthly 1-2 hour long ad-hoc screen
> sharing and video discussion for Org-mode?
>
> I'm offering to schedule and moderate the first few events. I'd
>
On Wed, Aug 31, 2022 at 4:19 PM Sébastien Miquel
wrote:
> Hi,
>
> I've been using tags on special blocks, src blocks and other, for two
> purposes:
>
> 1. to control which blocks get exported, using the `#+exclude_tags`
> property.
> 2. to fine tune the export, according to tags, of
On Wed, Jul 20, 2022 at 4:07 AM Uwe Brauer wrote:
> 2. Second code
>
> (defun test/set-property-at-heading ()
> "Function to be called at the beginning of an Org heading."
> (interactive)
> (let ((el (org-element-at-point)))
> ^el is defined but not used.
> (org-set-property
On Tue, Jul 19, 2022 at 12:58 PM Uwe Brauer wrote:
>
> > On Tue, Jul 19, 2022, 10:54 AM Uwe Brauer wrote:
>
> > Try replacing the `org-set-property` form to:
>
> > (org-set-property "New" "[]")
>
> This does not anything (besides garbage collecting)
>
Did you replace only the
On Tue, Jul 19, 2022, 10:54 AM Uwe Brauer wrote:
>
>
> #+begin_src elisp :noexport
> (defun my-set-property-at-heading ()
> "Function to be called at the beginning of an Org heading."
> (interactive)
> (let ((el (org-element-at-point)))
> (org-set-property "New" (org-element-property
Check out org-map-entries. I have one example here:
https://scripter.co/looping-through-org-mode-headings/#example-modifying-a-property-in-all-headings
.
On Tue, Jul 19, 2022, 4:16 AM Uwe Brauer wrote:
>
>
> Now, I would add to all subheadings a new property, say
>
> :Received: [ ]
>
> Whose
On Fri, Jul 8, 2022, 9:07 AM Gerardo Moro wrote:
> Hi,
>
> I recently discover the Obsidian Media Extended plugin (
> https://www.youtube.com/watch?v=GQXVWtNkeZw) to take notes while watching
> videos / listening to audios with keybindings to stop the video and create
> timestamps with link to
On Wed, Jul 6, 2022 at 11:17 AM Uwe Brauer wrote:
> Hi
>
> I have a file that contains a list as:
>
>
> 1.1 Funciones de una variable
>
> 1.1.1. Catálogo de funciones. Translaciones y dilataciones
>
> 1.1.2. Derivación
>
> 1.1.2.1. Optimización. Tasa de cambio
>
> 1.1.2.2. Aproximación de
On Fri, Jun 17, 2022 at 8:50 AM Cletip Cletip wrote:
> Final question : why do you use description lists and not another ?
I use description lists *heavily*.
1. For description lists of course.. where the "description" part is a
bit verbose and plain lists don't look at that elegant
For
On Sun, Jun 5, 2022, 9:40 AM Kaushal Modi wrote:
>
> Have you moved those repos elsewhere?
>
I kept on looking at the release 0.4 commit message on the org-contrib and
didn't realize that the "release notes" referred in that Mastodon thread
are at the different place
://fosstodon.org/@bzg/108424011487959609
--
Kaushal Modi
On Wed, Jun 1, 2022 at 1:32 AM Phil Estival wrote:
>
>
> * lisp/ox.el (org-export--skip-p): no longer export single-line
> comments as blank lines which did break paragraphs in two.
This is a pretty big breaking change. In your next PATCH email, I see
that you are also modifying the test that
On Mon, May 30, 2022 at 7:45 PM Ihor Radchenko wrote:
> Your code__collapse_all_posts block makes use of hide-subtree from
> outline.el. Please, do not use it. outline.el is no longer considered
> compatible with Org. It was not in the past, and even more so now. This
> has been announced in
On Mon, May 30, 2022, 7:45 PM Ihor Radchenko wrote:
> Kaushal Modi writes:
>
> > I was trying to create a minimal reproducible example for a different
> > issue and I ended up with this other issue that I didn't expect and so
> > I am reporting that first.
> >
:00
:END:
=
Hit TAB once again, you will see:
=
* Image / Figure :image:
** Image links...
=
Now if you move the point to line 69 (* Image links), hitting the TAB
will not do any kind of cycling at all.
--
Kaushal Modi
On Thu, May 26, 2022 at 1:36 PM João Pedro wrote:
>
> On Thu, May 26 2022 20:20, Ihor Radchenko wrote:
>
> > I think that you can simply open an issue in his Github repo.
>
> I reached out to him on e-mail, if he doesn't reply there I'll create
> the issue. Thanks!
Just saying this based on my
On Wed, May 25, 2022 at 11:09 AM Uwe Brauer wrote:
>
> Hi
>
> Sometimes I only want to convert/export a region or a paragraph of an
> org file to another format, most likely as html or latex.
> I cannot find such a functionality also not in the package system
> does anybody knows about such a
On Mon, May 23, 2022 at 10:33 AM Juan Manuel Macías
wrote:
> I think this idea was suggested by Ihor in a thread from a few months
> ago (I don't remember which one), but since other topics were discussed,
> the idea remained a bit in limbo. I still find the idea very
> interesting, and I think
On Tue, May 17, 2022 at 12:24 PM Guillaume MULLER
wrote:
>
> I noticed that hitting Meta-Return in org in Doom does not behave as in
> Vanilla Emacs. If I have (with <> being the cursor):
>
> * outline 1
> ** outline 2
>+ no<>te1
>+ note2
>
> In Vanilla Emacs, hitting M-Ret (i.e. calling
On Sat, May 14, 2022 at 5:39 AM Ihor Radchenko wrote:
>
> I just tried again on the latest main and I cannot reproduce anymore.
> Though I do see the problem on bugfix.
>
> Can you please check again on your side?
I confirm -- I cannot reproduce the bug in Org mode version 9.5.3
> Allen Li writes:
>
> > There appears to be a regression in the behavior of C-u C-u C-u TAB on
> > master (at aea24b3feafb9c389dc5933005928462bb20c4f8).
> >
> > C-u C-u C-u TAB is supposed to show everything including drawers, but on
> > this test file it does not show property drawers:
Thanks
Also check out the {{{time}}} macro if you want complete control on
the formatting of the date string.
Example Org snippet:
=
#+date: {{{time(%Y-%m-%d)}}}
#+options: toc:nil author:nil
See the ~{{{time}}}~ macro in [[info:org#Macro Replacement][org#Macro
Replacement]].
The format passed to
On Mon, May 9, 2022 at 5:44 PM Kaushal Modi wrote:
>
> I have now sent this to Emacs bug tracking:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55342
Thanks for the debug[1] Ihor!
This issue was quickly fixed on Emacs master in
https://git.savannah.gnu.org/cgit/emacs.git/c
done 55342
On Tue, May 10, 2022 at 1:06 AM Lars Ingebrigtsen wrote:
>
> Ihor Radchenko writes:
>
> > The code above always skips a bibtex entry starting at bob.
> > Hence, the provided example bibliography is parsed as empty, which is
> > not expected by Org.
>
> This should now be fixed on the
I have now sent this to Emacs bug tracking:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55342
On Mon, May 9, 2022 at 10:21 AM Kaushal Modi wrote:
> Can someone using emacs
> built from master branch confirm that they see this same error when
> `org-cite-process-bibliography` is called? It should be reproducible
> without using ox-hugo too.
Alright I was able to confirm t
On Thu, Nov 25, 2021 at 6:21 AM juh wrote:
> With cite_export: basic I get
>
> Wrong value for ENTRY-OR-KEY: nil
Hello,
I saw the ox-hugo CI fail with emacs master (29.0.50) over the past
few days with this backtrace, but this error is probably not related
to ox-hugo, and I need help confirming
On Thu, Apr 28, 2022 at 10:44 AM Ihor Radchenko wrote:
> I am not going to fix this just yet unless it is critical. It does not
> look like this bug is common.
It's not time-critical, but it would be good to fix this bug. It's not
just the Org link syntax.. any Org markup is fontified inside
-style to overlays, and refresh that Org
buffer, I see the square brackets around asdf in the src block (as
expected).
Org mode version 9.5.3 (release_9.5.3-458-g1ed9e4)
--
Kaushal Modi
On Fri, Dec 17, 2021 at 11:34 PM Ihor Radchenko wrote:
>
> Kaushal Modi writes:
>
> > I actually run a wrapper script to update Org and that has all that:
> > ...
> > I verified that at least the git hash was latest as of then:
> > release_9.5-364-g*de022e*
-indent, untabify
patch 2: Fix for the inf-loop
Can someone please review and apply these patches to the org-contrib repo?
[I am unable to commit using ssh/git: protocol (only https is allowed)
based on the network restrictions at work.]
Thanks!
--
Kaushal Modi
0001-lisp-org-eldoc.el-Whitespace
ction
((string= lang "php") (if (require 'php-eldoc nil t) (progn
(php-eldoc-function ((or (string= lang "go") (string= lang
"golang")) (if (require 'go-eldoc nil t) (progn
(go-eldoc--documentation-function (t (let ((doc-fun
(org-eldoc-get-mode-local-documentation-function lang)) (callback (car
args))) (if (functionp doc-fun) (progn (if ... ... ...
org-eldoc-documentation-function(#f(compiled-function (string
plist) #))
=
Recipe to create this error:
1. Create a file test.org with these contents:
#+begin_src org
,#+html: foo
#+end_src
2. emacs -Q
3. Load/evaluate org-eldoc.el from
https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/org-eldoc.el
4. Open the test.org file and place the point *inside* the org src block
5. eldoc error: (error Lisp nesting exceeds ‘max-lisp-eval-depth’)
-
Upon inspecting the `org-eldoc-documentation-function` function, I
don't see a reason why the control should enter the default of `t'
case if the src lang is "org". Just returning with nil works for me if
the lang is "org". I will send a patch for this in a follow-up email.
--
Kaushal Modi
On Wed, Apr 13, 2022 at 7:38 AM Max Nikulin wrote:
>
> On 13/04/2022 01:26, Kaushal Modi wrote:
> > On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
> >
> >> There are a some problems with info links outside of Emacs:
> >> - Export to PDF
> >
>
On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
> There are a some problems with info links outside of Emacs:
> - Export to PDF
Yeah, I recently realized that I will need to add custom support for
exporting info: links using ox-hugo. I made a small blog post out of
this learning:
On Mon, Apr 11, 2022 at 10:53 PM Vikas Rawal wrote:
>
> For a major project like this, I would just put these in a separate file, and
> include it using #+INCLUDE:
Org has a special keyword for the purpose of including *just the setup
stuff*: #+setupfile
See (org) Export Settings.
#+include
On Mon, Apr 11, 2022 at 8:35 AM Kaushal Modi wrote:
> I believe I am missing out something basic with inserting info: links
> in Org documents.
Yes, I was missing out on something :)
To my future self:
1. When in Info buffer, do M-x org-store-link (typically a user binds
this to C-c l:
uot;[[info:(org)
External Links]]" would work as well. But I think I am missing out on
some flow that would make the above manually editing in step 3
unnecessary.
How do you insert info: links efficiently?
--
Kaushal Modi
On Thu, Apr 7, 2022 at 12:30 PM William Denton wrote:
> I'm using macros to format names in a LaTeX export, like so:
>
> on export and LaTeX will format it. That works fine. But in an index of
> names,
> if I want
>
> {{{m(Denton, William)}}}
>
> then Org takes that as two arguments to the
On Mon, Apr 4, 2022 at 10:34 AM wrote:
>
> I would like to know why does a list need 2 blank lines instead of 1?
> For what reason exists this rule?
>
- 1 blank line in a list item with create a paragraph break as I showed in
my example earlier. It will not end the list item or list.
- So we
On Mon, Apr 4, 2022, 12:06 AM Ihor Radchenko wrote:
>
> I think your examples are a bit misleading.
I have the indentations correct in my three examples.
A list item continues until
> there are _2_ blank lines or until the subsequent line is not indented >=
> current list item indentation:
>
On Sun, Apr 3, 2022, 4:29 PM wrote:
> Hello togehter,
>
> is it usual to have auto-fill-mode (automatic new-line after n
> characters) turned on in org or org-roam (including fill-column set e.g.
> to 80)?
>
I cannot comment on that. Enabling auto-fill-mode is user preference.
Or let me ask
Hello,
Just pinging here again. Can someone confirm this bug?
--
Kaushal Modi
On Tue, Mar 1, 2022, 10:10 PM Kaushal Modi wrote:
> Hello,
>
> I believe I have come across a corner case issue where the inline src
> block element doesn't get parsed as one, if:
>
> 1. That src
e at least since 2015.
Thanks!
--
Kaushal Modi
On Sun, Mar 13, 2022, 6:55 AM Sébastien Gendre wrote:
> Hello everyone. _o/
>
> When I export an Org file to LaTeX and finally PDF, the code blocks and
> quotes often exceed the width of the page.
>
Hello _o/
I fixed[1] that problem by using the LaTeX minted package that allows
wrapping around
On Sun, Mar 13, 2022, 8:23 AM wrote:
> In real I (try to) use ox-hug to export my org-files (org-roam-v2) to
> markdown (and later to HTML).
>
> After analyzing the my debug output [1] the ox-hugo people pointed me to
> org-roam community because the error is "thrown" (correct term in
>
Hello Christian,
tl;dr: If you decide to learn how to use Hugo (read its docs, ask questions
on its forum, etc.), this[1] should solve the issues you have faced so far.
---
Details:
On Fri, Mar 11, 2022 at 7:04 AM wrote:
>
> ox-hugo with hugo is often mentioned in the context. But ox-hugo is
- abcdefg abcdefg abcdefg abcdefg `[[abc def][bar]]'.
=
Note that incorrect export of the inline src block in section 1 above.
The remaining sections exports correctly because either the inline src
block is not in a list item, or it doesn't wrap to the next line.
--
Kaushal Modi
On Mon, Feb 28, 2022 at 3:34 PM Kaushal Modi wrote:
>
> On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
> >
> > Hej,
> >
> > I have noticed that properties that stretch over multiple lines using
> > the :value+: syntax are ignored by org-element-propert
On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
>
> Hej,
>
> I have noticed that properties that stretch over multiple lines using
> the :value+: syntax are ignored by org-element-property and therefore
> also by e.g. org-export-get-node-property when exporting to ics via
> ox-icalendar.el
On Wed, Feb 23, 2022 at 7:37 AM Ihor Radchenko wrote:
>
> Dear all,
>
> Since there is at least a couple of people who might be interested, lets
> try to meet online on jitsi and debug performance issues you experience
> because of Org mode. Probably some time this Saturday (Feb 26). I am
>
On Tue, Feb 22, 2022, 12:34 AM Ihor Radchenko wrote:
>
> I am wondering if many people in the list experience latency issues.
> Maybe we can organise an online meeting (jitsi or BBB) and collect the
> common causes/ do online interactive debugging?
>
+1
I have seen few people see this issue on
> It is already in the main branch, AFAIU. I assume you mean it should be
> back-ported to bugfix branch. If that's the case, I don't know. This is
> a new feature, and not a critical one: there are workarounds, as you
> found out.
Yes, sorry, I meant the bugfix branch.
> This should be
Hello Nicolas,
> Since you are probably busy, I implemented this on your behalf. The new
> behaviour is in main branch. Thank you.
>
Can this commit[1] be merged into the main branch. Locally on my
machine, I use org built from main and something like this was working
fine:
#+cite_export: csl
On Sun, Feb 13, 2022, 4:18 AM Jeremie Juste wrote:
> Hello Cash,
>
> Many thanks for reporting but I cannot reproduce the error with my current
> version of emacs and org-mode. Could you specify the version of org-mode
> and emacs you are currently using?
>
> * test
> :PROPERTIES:
> :ID:
version: GNU Emacs 28.0.91 (build 7, x86_64-pc-linux-gnu, GTK+
Version 3.22.30, cairo version 1.15.12) of 2022-01-25, built using
commit 7eca80b20444f7bd7bcb6a66a9054e029f0e7013.
--
Kaushal Modi
Hi Samuel,
On Sun, Jan 16, 2022 at 12:06 PM Samuel Banya wrote:
>
> I am planning to use Emacs to create Org Mode files for the few main sections
> of my site that aren't the Art Gallery page itself.
>
> I'm trying to figure out how to get a modern Wordpress looking Org generated
> HTML page
Hello Ihor,
> The issue here had nothing to do with hanging. You are probably seeing
> yet another bug.
ok.
> By hang, do you mean that even C-g does not restore responsiveness?
Typically, within a second of doing C-c C-q, I would know that the
buffer is going to freeze, and if I do C-g soon
to nil, Emacs stopped hanging.
Looking at your bug report, I believe that the issue I am seeing with
cache and Org tags could be very much related. So thanks for
submitting this.
--
Kaushal Modi
On Mon, Jan 10, 2022 at 8:35 AM Timothy wrote:
>
> FWIW, I think it would be good to be internally consistent. #+RESULTS is
> currently one of the few keywords inserted in upper case. Unless there’s a
> good
> reason to distinguish it from other keywords (perhaps an argument could be
> made
>
On Sun, Jan 9, 2022 at 3:01 PM Nicolas Goaziou wrote:
>
> I suggest to use
>
> (org-element-interpret-data (org-element-contents special-block))
That does it!! Thank you!
Also thanks to Juan and Charles who helped lead me to the final solution.
> On Sat, Jan 8, 2022 at 10:01 PM Berry, Charles
> wrote:
Hi Charles,
I used your minimal example to show the issue I am seeing when using
ox-md as the base exporter.
=
#+property: header-args :results none :exports none :eval never-export
#+options: toc:nil
* Define newmd
On Sat, Jan 8, 2022 at 10:01 PM Berry, Charles wrote:
>
>
> A simple one here:
>
> #+begin_src emacs-lisp
> ;; minimal backend with latex parent
> (org-export-define-derived-backend 'newlatex 'latex
> :translate-alist
> '((special-block . org-newlatex-special-block)))
>
> ;; special
> What am I missing?
>
> It seems like you want your derived backend to transcode special blocks
> somewhat differently than the parent backend. And adding a special block
> export filter doesn't quite do the job.
I tried out the example Juan posted and it works perfectly well. But
it would
On Thu, Jan 6, 2022 at 2:33 PM Juan Manuel Macías
wrote:
> I just realized that there is a much simpler solution for your katex
> environment :-)
>
> You can use an example block, and define your custom environment using
> the attribute :environment
Sorry, but this exporter is derived from md,
On Thu, Jan 6, 2022 at 1:27 PM Juan Manuel Macías
wrote:
> I think one possibility would be using a parse tree export filter:
>
> #+BIND: org-export-filter-parse-tree-functions (katex-verbatim)
> #+begin_src emacs-lisp :exports results :results none
> (defun katex-verbatim (tree backend info)
>
that enables the verbatim mode (prevent Org from
replacing the Org entities, do the sub/superscript expansion, etc.)?
--
Kaushal Modi
On Fri, Dec 17, 2021 at 11:34 PM Ihor Radchenko wrote:
> > There's a setup included in there; I forgot about that. If you don't mind
> > trying it again, this would download everything needed:
>
> Thanks! I was able to follow your steps this time.
>
I really appreciate making this extra effort
On Thu, Dec 16, 2021 at 10:16 AM Ihor Radchenko wrote:
>
> FYI, it is suspicious. You should be at 9.5.1. Maybe you forgot to make
> clean; make autoloads.
>
I actually run a wrapper script to update Org and that has all that:
=
# cmds to update to latest commit on git main branch
> Can you:
> 1. Update Org to latest version
> 2. set org-element--cache-self-verify to 'backtrace
> 3. set org-element--cache-self-verify-frequency to 1.0
> 4. Try to reproduce the warning you are seeing
> 5. If you still see it, post the full warning text including the
>backtrace (below the
On Wed, Dec 15, 2021 at 9:29 PM Kaushal Modi wrote:
>
> Can you help fix this?
>
Also looking closely, I am seeing a different warning:
Warning (org-element-cache): org-element--cache:
(org-hugo-export-wim-to-md) Cached element is incorrect in *Ox-hugo
Pre-processed ox-hugo-manua
On Mon, Nov 8, 2021 at 1:05 AM Ihor Radchenko wrote:
>
> I was able to reproduce the issue. This is a bug on ox-hugo side.
> `org-hugo--get-pre-processed-buffer' inserts text with
> inhibit-modification-hooks bound to non-nil, which breaks
> org-element-cache. The cache is enabled by default in
On Sun, Dec 5, 2021 at 4:12 AM Nicolas Goaziou
wrote:
> Hello,
>
> Ihor Radchenko writes:
>
> > Sorry, but tests are still slow for me after the update.
> > If I run the test from inside Emacs with ert, things got better, but
> > make BTEST_RE="^test-org-cite/adjust-note" test
> > still takes
external ssh access.
>From de607dff518eaa91149ff1aa8c255f67fb6ee887 Mon Sep 17 00:00:00 2001
From: Kaushal Modi
Date: Tue, 30 Nov 2021 20:37:10 -0500
Subject: [PATCH] org: Remove `org-comment-line-break-function'
* lisp/org.el: Remove `org-comment-line-break-function' and let
`comment-l
On Sat, Dec 4, 2021, 5:25 PM Tim Cross wrote:
>
> Given that Nicholas cannot remember the reason for the original function
> and suspects it was meant to be an internal only function, I think this
> patch is probably the best way forward and should be applied.
>
Thanks. Nicolas asked me to add
On Thu, Dec 2, 2021, 8:08 AM Vincent Breton
wrote:
> Hi,
>
>
> Emacs and Emacs Org documentation, and lot of others GNU products use
> Texinfo to generate their own documentation to different formats.
The Org mode documentation switched to Org format few years back:
d this patch work?
=
>From 1a9187b82ed8d4e8d54ddd369a44d34295281fc3 Mon Sep 17 00:00:00 2001
From: Kaushal Modi
Date: Tue, 30 Nov 2021 20:37:10 -0500
Subject: [PATCH] org: Remove `org-comment-line-break-function'
* lisp/org.el: Remove `org-comment-line-break-function' and let
`comment-line
On Tue, Nov 30, 2021, 6:29 PM Tim Cross wrote:
>
> Regardless, I think that unless we understand the purpose of
> insert-before-markers-and-inherit, we should make the patch such that it
> still calls that function. Even if fill-prefix is nil there is
> probably a good reason why the markers and
On Tue, Nov 30, 2021 at 3:20 PM Marco Wahl wrote:
>
>
> diff --git a/lisp/org.el b/lisp/org.el
> index 1a1375461..fdeec0d67 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -19695,7 +19695,8 @@ non-nil."
>(save-excursion (forward-char -1) (delete-horizontal-space))
Hello all,
I am following up on this issue with ob-shell and sessions.
I had posted the recipe to reproduce the issue few months back, and it
still applies; ref:
https://list.orgmode.org/CAFyQvY2AeToQc2G=e+de4votetfbkvisenipypw1y-feu1o...@mail.gmail.com/
Thanks!
--
Kaushal Modi
On Fri, Nov 5, 2021, 9:48 AM Ihor Radchenko wrote:
>
> I am not sure if we are dropping Emacs 25 just yet. However, there is
> currently more than one place in Org that does not work on Emacs 25.
> See https://list.orgmode.org/87zgqu6081.fsf@localhost/T/#t
>
> If compilation is critical for you,
On Fri, Nov 5, 2021 at 10:25 AM Ihor Radchenko wrote:
> Fixed on main. Thanks for reporting!
>
Thanks! I confirm the fix.
rg-persist-write((org-element--headline-cache org-element--cache)
#)
org-persist-write-all(#)
org-persist-write-all-buffer()
kill-buffer("NEWS")
Are there any pointers on how to fix this?
Thanks!
--
Kaushal Modi
On Fri, Nov 5, 2021 at 9:27 AM Kaushal Modi wrote:
> Hello,
>
> On the topic of xdg, I pulled Org from main branch today and tried to
> build it but it's failing with:
>
> org-persist.el:32:1:Error: Cannot open load file: No such file or
> directory, xdg
>
> Anybody e
On Fri, Nov 5, 2021 at 9:27 AM Kaushal Modi wrote:
> Hello,
>
> On the topic of xdg, I pulled Org from main branch today and tried to
> build it but it's failing with:
>
> org-persist.el:32:1:Error: Cannot open load file: No such file or
> directory, xdg
>
> Anybody
Hello,
On the topic of xdg, I pulled Org from main branch today and tried to build
it but it's failing with:
org-persist.el:32:1:Error: Cannot open load file: No such file or
directory, xdg
Anybody else seeing this?
On Fri, Jul 23, 2021 at 10:07 AM Marco Wahl wrote:
> André A. Gomes writes:
>
> > The project's documentation refers to headings and headlines as
> > synonyms. Relying on a single definition would be beneficial.
>
> Agreed. E.g. no more thinking waste about the question if it is
> headline or
Hello,
On Fri, Jul 16, 2021 at 12:35 PM Bruce D'Arcus wrote:
> On Fri, Jul 16, 2021 at 12:07 PM William Denton wrote:
>
> > However, I was a bit surprised when I found that a commented line starts
> a new
> > paragraph.
>
> I hadn't yet discovered that, but I think it should be considered a
>
Hi Nick,
On Tue, Jun 8, 2021 at 11:54 PM Kaushal Modi wrote:
>
> Thanks! I tried out your patch and it does fix the truncation of results
> output. Though, it retains the shell prompt in the first eval block and
> removes it only from the second eval block onwards.
>
I have on
On Thu, May 6, 2021 at 7:45 PM Nick Savage wrote:
> So I have a patch written that doesn't completely fix the problem, but
> maybe makes enough progress that someone else can figure it out.
>
> The issue is that comint-prompt-regexp is reading the "% " as a prompt,
> and taking everyone off
1 - 100 of 807 matches
Mail list logo
