Visuwesh 于2023年10月11日周三 23:36写道：
> >> + (caddr (read-multiple-choice
> >> + "What to do with dropped file?"
> >> + '((?a "attach" attach)
> >> + (?o "open" open)
> >> + (?f "insert file: link" file-link
> >
> > The dialog box is shown in the center of frame and I find it a little
> > inconven
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.
Emacs version: 29.1
Org-mode version: e1569918cc94253650781e83a09695739c93352f (latest in git)
Test document:
```
#+CAPTION: foo
# bar
```
This parses as a paragraph with the caption of foo and the body of "# bar" when
it should parse as a regular keyword followed by a comment.
Relevant org-syn
Steps to reproduce:
1. Build emacs 29.1
2. Build org-mode with revision 37d6bde27fe228cdadcb5cdaa09287872a508777
3. Run the following:
```
emacs -q --no-site-file --no-splash --batch --eval "(progn
(require 'org)
(setq vc-handled-backends nil)
(find-file-read-only \"org-mode/testi
Emacs version: Emacs 29.1
Org-mode version: e1569918cc94253650781e83a09695739c93352f (latest in git)
The org-mode syntax document[1] says that property drawers can exist in the
zeroth section with the format:
```
BEGINNING-OF-FILE
BLANK-LINES
COMMENT
PROPERTYDRAWER
```
Using this test document:
Ihor Radchenko writes:
> I am not sure if I like it.
Me neither. The problem is in the parentheses, IMHO. The Lisp
expression is enclosed in parentheses and so is the description:
(message "Hello") (Message Hello)
That indeed looks confusing! How about we swap the sides and remove one
pai
It was long time ago...
On 18/02/2022 07:47, Juan Manuel Macías wrote:
Otherwise, if you export to LaTeX with pandoc (v. 2.14.2), the result is
(to my surprise) correct:
#+begin_src sh :results latex
str="/lorem /ipsum/ dolor/"
pandoc -f org -t latex <<< $str
#+end_src
#+RESULTS:
#+begin_expor
[புதன் அக்டோபர் 11, 2023] Liu Hui wrote:
> Hi,
>
> Thanks for your work. I have two minor suggestions about the patch.
>
>> + (`file-link
>> + (let ((filename (dnd-get-local-file-name url)))
>> + (insert (org-link-make-string (concat "file:" filename
>
> I think it is better to abbreviate
> Uwe Brauer writes:
> The ref "remote(table1,@2$7..@>$7)" targets a range, containing all fields of
> colum 7. So, for each field, you get the same value: an array
> containing all the field values: [22, 19, 19].
> See (info "(org) References"), in the section:
>"Field coordinates in fo
> Fixed, on main.
Thanks!
--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc
Thanks!
> We aim to reduce config-dependent Org syntax in the long term.
Thats wonderful news! Sometimes this stuff can really surprise you. For
example, the structure of the document created by running `echo "1. foo\n
1.bar\n1.baz\n\t1.lorem"` changes based on the user's **tab-width**!
Hi,
Thanks for your work. I have two minor suggestions about the patch.
> + (`file-link
> + (let ((filename (dnd-get-local-file-name url)))
> + (insert (org-link-make-string (concat "file:" filename
I think it is better to abbreviate the file name for file-link, so it
would be consistent
Max Nikulin writes:
>> No, **bold** it is not a bug. The parser is recursive with inner markup
>> not "seeing" its parent. So, we first parse the outer bold and then
>> continue parsing the contents separately, as *bold*.
>
> I just find the following rather confusing:
>
> (org-export-string-as "
On 11/10/2023 16:15, Ihor Radchenko wrote:
Max Nikulin writes:
Isn't nested bold for "**bold**" a bug? Generally it is not allowed and
*b1 *b2* b3*
is parsed as bold only for "b1 *b2".
No, **bold** it is not a bug. The parser is recursive with inner markup
not "seeing" its parent. S
Max Nikulin writes:
> Isn't nested bold for "**bold**" a bug? Generally it is not allowed and
>
> *b1 *b2* b3*
>
> is parsed as bold only for "b1 *b2".
No, **bold** it is not a bug. The parser is recursive with inner markup
not "seeing" its parent. So, we first parse the outer bold and the
Edgar Lux writes:
> Emacs : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.36,
> cairo version 1.17.6)
> of 2023-01-03
Hopefully, fixed now.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=37d6bde27
(the reproducer was found in a private email thread, and is
William Denton writes:
> I updated things from source today and got an error when trying to view my
> agenda:
>
> M-x org-agenda
> t
>
> showed the error
>
> Wrong type argument: stringp, nil
>
> In *Messages* I saw:
>
> Press key for agenda command (unrestricted):
> org-agen
Ihor Radchenko writes:
>> if I have the following heading :
>>
>> * A test
>> [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
>> <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>
>>
>> The "org interval" are not respected for the inactive timestamp. See what
>> is the result in org-agenda :
>>
>>
> Bruno Barbier writes:
> The change seems to come from this commit:
>
>commit d7a55bbd537314d2776b082bd92a1a08b3edc84e
>Date: Wed Sep 28 12:07:14 2022 +0800
>org-latex-export-to-latex: Do not suppress major modes in babel
>
Thank you for finding the culprit.
> Ihor Radchenko writ
19 matches
Mail list logo
