On Tue, Dec 27, 2022 at 2:26 PM Ihor Radchenko wrote:
>
> Luca Ferrari writes:
> Could you please provide more details about what is happening?
> What exactly do you do to copy the link?
> See https://orgmode.org/manual/Feedback.html#Feedback
>
Imagine I've this org fragment:
Link: [[https://fo
i meant bulk.
On 1/11/23, Jean Louis wrote:
> * Nick Dokos [2023-01-10 20:53]:
>> IIUC, you can use `org-map-entries` to apply the function `org-todo`
>> (or a different function if you want) to a collection of nodes in a
>> file that are specified through tags/properties matches:
>>
>>(org-
Hello,
This issue is best explained with this small example.
1. Create this Org buffer:
=
#+options: author:nil toc:nil
* Post 1
:PROPERTIES:
:EXPORT_FILE_NAME: foo
:END:
* Post 2
=
2. Place the cursor at the end of :END:
3. C-c C-e C-s t A
You get this:
=
On Wed, Jan 11 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> Leo, could you please take a look?
>
> An earlier test is creating that *Org Babel Error Output* buffer.
>>>
>>> I will try to look into improving the tests so that we can trap the test(s)
>>> that is(are) creating
Org mode renders the following line in bold between the asterisks in the Emacs
window. It seems to be the last dot after the first asterisk that triggers the
assumed rendering bug.
┌
│ =org-*.css= and =org-*.css.el=
└
On the other hand, the same line exports properly with both the ASCII a
On Wed, 11 Jan 2023 12:02:42 -0500 Ihor Radchenko wrote ---
> It looks like you lost all the individual commits and commit messages in
> the process.
>
> Could you please revert 4f319088ba5 and re-push in such a way that
> individual commits do appear on main?
Goodness! Sorry! T
* Nick Dokos [2023-01-10 20:53]:
> IIUC, you can use `org-map-entries` to apply the function `org-todo`
> (or a different function if you want) to a collection of nodes in a
> file that are specified through tags/properties matches:
>
>(org-map-entries #'org-todo "LEVEL=1" 'file)
>
> will ap
* Samuel Wales [2023-01-10 04:41]:
> idk if i understand your q but you can do agenda on tag and then batch
> command.
Thanks, what batch command do you mean?
Do you mean this one:
org-batch-agenda is an autoloaded Lisp macro in ‘org-agenda.el’.
(org-batch-agenda CMD-KEY &rest PARAMETERS)
Ru
Matt writes:
> I was not, thank you. I've since pushed.
This:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4f319088ba5f11d4b6adf808f39f11dfa52c08e4
?
It looks like you lost all the individual commits and commit messages in
the process.
Could you please revert 4f319088ba5 an
On Wed, 11 Jan 2023 06:53:41 -0500 Ihor Radchenko wrote ---
> I have the following Git configuration:
>
> u remote.origin.url
> yanta...@git.savannah.gnu.org:/srv/git/emacs/org-mode.git
>
> Are you using the same?
I was not, thank you. I've since pushed.
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, feel
Ihor Radchenko writes:
> +1
Done, thanks.
Kaushal, it should appear on GNU ELPA in a few hours.
Ihor, feel free to publish bugfix releases with no special permission
in the future.
--
Bastien
Bastien Guerry writes:
>> Can a new version of Org be tagged from the bugfix branch?
>
> Ihor, if you agree, I can release Org 9.6.1 today.
>
> We can continue to work on Org 9.6.2 for later merge in Emacs.
>
> The problem with `org-assert-version' can be dealt with later
> on, even if many users
Hi Kaushal,
Kaushal Modi writes:
> Can a new version of Org be tagged from the bugfix branch?
Ihor, if you agree, I can release Org 9.6.1 today.
We can continue to work on Org 9.6.2 for later merge in Emacs.
The problem with `org-assert-version' can be dealt with later
on, even if many users
Hello,
Can a new version of Org be tagged from the bugfix branch?
The below-reported bug was fixed quickly but the Elpa version of Org
doesn't yet see that fix.
My ox-hugo package uses the Elpa version of Org mode for the tests on
Github Actions, so my test suite has been failing for quite some
Michael Dauer writes:
> Yes, but the missing headings are within the narrowed subtree.
You are right.
What is happening here is `org-element-parse-buffer' skipping over the
folded heading:
When VISIBLE-ONLY is non-nil, don't parse contents of hidden
elements.
--
Ihor Radchenko // yant
Yes, but the missing headings are within the narrowed subtree.
Am Mi., 11. Jan. 2023 um 12:22 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > But within (org-with-wide-buffer) the collapsed branches should be
> visible.
>
> You have `org-narrow-to-subtree' inside
Matt writes:
> On Thu, 05 Jan 2023 06:21:16 -0500 Bastien Guerry wrote ---
> > My bad: I did not warn Emacs maintainers in time. Now it is done,
> > I will let you know when they grand you access to the Emacs project.
>
> I got an email from Eli on Thursday saying I was added. I've s
Michael Dauer writes:
> But within (org-with-wide-buffer) the collapsed branches should be visible.
You have `org-narrow-to-subtree' inside `org-with-wide-buffer':
1. `org-with-wide-buffer' widens the buffer
2. `org-narrow-to-subtree' narrows it to subtree
3. `org-element-parse-buffer' gets exec
But within (org-with-wide-buffer) the collapsed branches should be visible.
Ihor Radchenko schrieb am Mi., 11. Jän. 2023, 11:02:
> Michael Dauer writes:
>
> > I would expect both output rows to be identical. But it seems
> > that (org-with-wide-buffer) has no effect on (org-element-parse-buffer
Leo Butler writes:
> Leo, could you please take a look?
An earlier test is creating that *Org Babel Error Output* buffer.
>>
>> I will try to look into improving the tests so that we can trap the test(s)
>> that is(are) creating that error buffer.
>
> See the attachment. There are f
Ihor Radchenko writes:
Ilya Chernyshov writes:
(defun org-datetree--find-create
@@ -169,18 +167,19 @@ component. If INSERT is non-nil and
there is no match then it is
inserted into the buffer."
(when (or month day)
(org-narrow-to-subtree))
- (let ((re (format regex-template ye
Daniel Fleischer writes:
> Ihor Radchenko writes:
>
>> Can you try to test the attached patch?
>
> Looks good. Now these work again: `cdlatex-dollar`, inserting symbols
> using ` outside math environments and inserting cdlatex environments
> with completion also outside math environments. Need t
Michael Dauer writes:
> I would expect both output rows to be identical. But it seems
> that (org-with-wide-buffer) has no effect on (org-element-parse-buffer)
> with VISIBLE-ONLY argument.
> While I believe this is a bug, I would also appreciate hearing about
> possible work-arounds.
This beha
Sterling Hooten writes:
> Thanks for the instructions, this is my first patch.
>
> I think calling `nonew’ invalidates the argument `no-indent’ as
> `org-bibtex-put’ eventually
> calls `org-entry-put’ which uses `org-indent-line’. I’m not sure what’s the
> best way to handle that.
You are in
I see a potential bug here: (org-element-parse-buffer) with VISIBLE-ONLY
does not include regions made visible with (org-with-wide-buffer).
Test (Have h2.2.1 collapsed before running it.):
>>>
* h1
** h2
*** h2.1
*** h2.2
#+begin_src elisp
(org-with-wide-buffer
(org-narrow-to-subtree)
(goto-char
26 matches
Mail list logo
