Ihor Radchenko writes:
> Joseph Turner writes:
>
>>> You probably meant to link to some different ticket here.
>>
>> https://todo.sr.ht/~ushin/ushin/188
>
> So, you want an equivalent of `org-safe-remote-resources'.
For now, we've added a command `hyperdrive-mark-as-safe`, which causes
automati
Aloha.
So, even this MWE, the export to *.ics does not work as expected. The
test.ics file has no events when
M-x org-icalendar-export-to-ics
is invoked.
= Contents of test.org listed below
=
-*- org-icalendar-use-deadline: (todo-due); -*-
MY PROJEC
Yes, you are right !
With head there is no problem (probably forgot to adjust my load-path
before ...)
Thanx for the help !
Rgards
Marc
Am 08.06.2024 um 17:28 schrieb Ihor Radchenko:
Marc-Oliver Ihm writes:
Hi all,
If I have this simple buffer:
* foo
*** bar
*
Well, it doesn't seem to work as expected. I'll create a test setup and
see if I can isolate what is not working with just a few TODOs.
J.
On 6/8/24 10:44, John Helly wrote:
Mahalo.
That allowed the command (org-icalendar-export-to-ics) to succeed but
it didn't produce the desired results.
Mahalo.
That allowed the command (org-icalendar-export-to-ics) to succeed but it
didn't produce the desired results. I'll try adding other values and
see if the situation improves.
J.
On 6/8/24 10:38, Ihor Radchenko wrote:
John Helly writes:
I modified the variable specification to be:
John Helly writes:
> I modified the variable specification to be:
>
> -*- org-icalendar-use-deadline: event-if-not-todo; -*-
> and get the following error:
>
> 'Wrong type argument: listp, event-if-not-todo'
That's because the value should be a list.
-*- org-icalendar-use-deadline: (event-if-
Aloha.
I modified the variable specification to be:
-*- org-icalendar-use-deadline: event-if-not-todo; -*-
and get the following error:
'Wrong type argument: listp, event-if-not-todo'
So it's reading the specification but seems that the syntax is
incorrect. I don't seem to be able to find
John Helly writes:
> Sure. Thanks for the reply.
>
> 1) I put this line at the top of the org file
>
> -*- org-icalendar-use-deadline: t; -*-
This is not right. According to the docstring:
org-icalendar-use-deadline is a customizable variable defined in
ox-icalendar.el.
Value
Max Nikulin writes:
> It seems the org-ruby project link on the https://orgmode.org/tools.html
> page is outdated and should be updated to the repository of its current
> maintainer.
>
> I suggest to move the link to the Import&Export section since the
> primary purpose of the project is conve
Suhail Singh writes:
> Ihor Radchenko writes:
>
>> Accidentally deleted newline here* Heading 2
>
> Are there situations which result in such accidental newline deletions
> that are likely to not be immediately caught if not prompted by the
> checker? Or was the checker added preemptively?
I h
Bastien Guerry writes:
>> I do not see much problem listing announcements, blogs, and requests
>> there; but bug reports are probably not something we want to show to
>> newbies right at the front page.
>
> I restricted it to "news": https://tracker.orgmode.org/news.org
Looks like we do not have
Hi,
It seems the org-ruby project link on the https://orgmode.org/tools.html
page is outdated and should be updated to the repository of its current
maintainer.
I suggest to move the link to the Import&Export section since the
primary purpose of the project is conversion to HTML, Markdown, o
Ihor Radchenko writes:
> Accidentally deleted newline here* Heading 2
Are there situations which result in such accidental newline deletions
that are likely to not be immediately caught if not prompted by the
checker? Or was the checker added preemptively?
Perhaps the checker should simply be
Suhail Singh writes:
> On a related note, what specific situation(s) was this checker intended
> to help the user in? I.e., what are the situations that could result in
> misplaced headings?
For example,
* Heading 1
* Heading 2* Heading 3
* Heading 4
or
* Heading
Some text inside.
Accidenta
Marc-Oliver Ihm writes:
> Hi all,
>
> If I have this simple buffer:
>
> * foo
>
> *** bar
> *** END
>
> i.e. one node with a single inline node.
> If now I place the cursor at the end of the buffer and invoke (org-reveal), I
> get stuck in an endless loop.
> (of course on
Andrea writes:
> ob-sql.el has a function org-babel-execute:sql. This function extracts
> the password to connect to your database of choice as dbpassword.
> It then uses it like this:
>
> (if dbpassword
> (format "PGPASSWORD=%s " dbpassword)
> "")
>
> If the password contains an
On 06/06/2024 01:06, Ihor Radchenko wrote:
Remember that older Org mode also did not have link paths searchable.
You are right, I forgot about it.
Since the feature was advertised in ORG-NEWS
Hidden parts of the links can now be searched and revealed during isearch
another entry should
Suhail Singh writes:
> Ihor Radchenko writes:
>
>> Oops.
>> I amended the fix now.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6c862699a
>
> It's better, but not quite there. For instance, tangle the block below
> into an org file and observe the reported warning.
>
> #+b
On 08/06/2024 06:48, Pedro Andres Aranda Gutierrez wrote:
I was reading through patch
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=212237bdbd6b5f372d11de5d1f8db12dcf649682
and reading:
+ ) ; Inside a block, where the chances to have heading a slim.
I can't make out what "to h
19 matches
Mail list logo
