Jens Schmidt writes:
> On 2023-07-22 15:48, Ihor Radchenko wrote:
>
>> I am not familiar with Gnus, but looking at the code, may it be that
>> a Gnus article is open when Gnus summary buffer is not?
>
> Theoretically yes, if you actively and malignantly kill the summary
> buffer, for example.
Max Nikulin writes:
> On 19/07/2023 09:36, Gavin Downard wrote:
>> +++ b/lisp/org-table.el
>> @@ -2253,8 +2253,7 @@ LOCATION is a buffer position, consider the formulas
>> there."
>> ((not (match-end 2)) m)
>> ;; Is it a column reference?
>>
On 2023-07-22 15:48, Ihor Radchenko wrote:
I am not familiar with Gnus, but looking at the code, may it be that
a Gnus article is open when Gnus summary buffer is not?
Theoretically yes, if you actively and malignantly kill the summary
buffer, for example. In practice and through Gnus key
Jens Schmidt writes:
> The most obvious symptom is this:
>
> - Create an nnselect group and open an article from that. In the
>article buffer, do M-x org-store-link RET, then paste the link with
>C-c C-l in some Org mode buffer. The resulting link looks like
>
>
Max Nikulin writes:
>> I cannot find anything blocking the proposed change.
>
> I have not found anything valuable as well. So the only conflict is
> named cell vs. named column.
> ...
I followed similar trace.
> So names after $ were used in the past, but only named fields are
> currently
On 22/07/2023 14:25, Ihor Radchenko wrote:
Max Nikulin writes:
Perhaps git blame for the manual may give some hints. If the change is
really old then org.texi (removed at certain moment) should be inspected
as well.
This has been added very, very long time ago. org-table has undergone
On 19/07/2023 09:36, Gavin Downard wrote:
+++ b/lisp/org-table.el
@@ -2253,8 +2253,7 @@ LOCATION is a buffer position, consider the formulas
there."
((not (match-end 2)) m)
;; Is it a column reference?
((string-match-p
Max Nikulin writes:
> My idea is to handle dropping of text into Org buffers. Currently it
> causes opening links in eww. I think, there are better options: convert
> from html to Org using pandoc and insert text, `org-capture',
> `org-store-link'. I have not tried to implement it. Currently
Hi all,
you might be interested in looking at my latest (very small) project - a blog
engine written on top of Org mode. Yes, yet another one - but each of the
existing solutions lacked something I needed.
Head on to GitLab (https://gitlab.com/mbork_mbork_pl/org-clive) or to my
blog post
Tags: patch
`org-store-link' has a number of related issues when storing links from
article buffers related to nnvirtual, nnselect, or nnir groups. I
describe them here in prose without providing a full repro case, which
would be somewhat difficult to set up. Just let me know if you think
you
Arthur Miller writes:
>> (org-link-set-parameters "http" :insert-description #'your-function)
>> (org-link-set-parameters "https" :insert-description #'your-function)
>
> Thanks, after some thinkering I got it:
>
> ...
> (org-link-set-parameters "http" :insert-description
Jonathan Gregory writes:
> On 21 Jul 2023, Ihor Radchenko wrote:
>
>> The png is still a full page on my side.
>
> That's not what I get. You're probably missing the paper settings:
>
> #+begin_src lilypond :exports none
> \version "2.20"
> \paper {
> indent=0\mm
> tagline=""
>
Mehmet Tekman writes:
>> P.S. There going to be Emacs meetup this Saturday, July 22
>> (https://emacs-apac.gitlab.io/announcements/july-2023/). I plan to be
>> there and, if you need it, we can try to resolve difficulties in more
>> interactive way.
>
> I am currently travelling this weekend,
Max Nikulin writes:
> Perhaps git blame for the manual may give some hints. If the change is
> really old then org.texi (removed at certain moment) should be inspected
> as well.
This has been added very, very long time ago. org-table has undergone
through major transformations since that
Thanks for fixing all the documentation issues I submitted today!
On Sat, Jul 22, 2023, at 2:58 AM, Ihor Radchenko wrote:
> "Tom Alexander" writes:
>
>> The documentation for plain links states that PATHPLAIN is:
>>
>>> A string containing non-whitespace non-bracket (()[]<>=) characters,
>>>
"Tom Alexander" writes:
> The documentation for plain links states that PATHPLAIN is:
>
>> A string containing non-whitespace non-bracket (()[]<>=) characters,
>> optionally containing parenthesis-wrapped non-whitespace non-bracket
>> substrings up to a depth of two. The string must end with
"Tom Alexander" writes:
> The documentation for line breaks says that PRE is:
>
>> Anything but backspace (`\`).
>
> I suspect this is supposed to say "backslash" (ascii 92) not "backspace"
> (ascii 8)
>
> Link to the documentation:
> https://orgmode.org/worg/org-syntax.html#Line_Breaks
"Tom Alexander" writes:
> The documentation for Inline Babel Calls mentions that opening and closing
> square brackets must be balanced within BODY but the grammar above it only
> defines NAME, ARGUMENTS, HEADER1, and HEADER2.
>
> Link to the documentation:
>
"Tom Alexander" writes:
> The documentation for Citations when specifying which syntactic elements have
> spaces between them references a "KEYCITES" syntactic element that does not
> appear anywhere else on the page.
>
> Link to the documentation issue:
>
19 matches
Mail list logo
