Thank you Ihor for finding such an important bug.
I've tried to pinpoint it.
I think it happens only when: first heading (row) is the first line of the
buffer.
To reproduce it:
* a
* b
* c
C-u C-c C-x C-c => runs `org-columns' with global argument.
Using a keyboard. Press M-, M-, M-.
Heading 'a'
Tim Landscheidt writes:
> But there is calendar-week-start-day which I would expect
> affected Emacs users to have customized.
It is not at all obvious that Org should be affected by calendar
customization. And we use different default - Monday, while
calendar-week-start-days defaults to Sunday.
Max Nikulin writes:
>>> #+BEGIN: clocktable :maxlevel 2 :scope agenda-with-archives
>>> :weekstart 7 :block thisweek :step day :fileskip0 :narrow 20!
>>^^
>>
>> should be :wstart -- let us know if it works!
>
> So at least some people expect 7, not 0. I would say, both v
Damien Cassou writes:
> Results are:
>
> - before commit: "a" length-src=5 length-dest=5
> - after commit: "a" length-src=5 length-dest=9
>
> After the commit, the result of `org-odt-plain-text` contains 4 more
> leading spaces. Is that the expected behavior or is that a bug?
Thanks
Ruijie Yu via "General discussions about Org-mode."
writes:
> This is a tentative patchset for orgweb zh_CN translation.
Thanks!
> * How do I change the heading for the footnote section? In
> particular, can I set it in a file- or dir-local variable, or in the
> setup.org file? This
Ihor Radchenko writes:
> Fixed, on bugfix.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=60ce29dc4
thank you very much.
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
On 11/04/2023 17:09, Ihor Radchenko wrote:
Max Nikulin writes:
So at least some people expect 7, not 0. I would say, both variants
should be acceptable.
Would you be interested to make a patch?
Not really. I expect something like
(let* ((ws (mod (or wstart 1) 7))
(diff
Hello,
I have Emacs 28 on one machine and this build 29 on this machine--both running
on Windows 10. I've encountered the same bug on both builds of Emacs. I believe
it's a bug.
To reproduce the behavior, first make a link that begins a line, such as:
[[www.google.com][link]]
Org Mode will tu
On 2023-04-11, at 13:34, Max Nikulin wrote:
> On 11/04/2023 17:09, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>> So at least some people expect 7, not 0. I would say, both variants
>>> should be acceptable.
>> Would you be interested to make a patch?
>
> Not really. I expect something like
>
Hello Ihor,
Thanks for your response. I made some changes accordingly, which can be
found here: https://git.sr.ht/~ruijieyu/orgweb/tree/translate/zh-CN--v2 .
More responses inline below.
Ihor Radchenko writes:
> Ruijie Yu via "General discussions about Org-mode."
> writes:
>
>> This is a te
I'm exporting the following org file (left-side) to a LaTeX pdf file.
The org file contains the multiple dashes in the ~code~ =verbatim=
format. The exported PDF file doesn't have the correct number of dashes.
|+---|
| Original org | Exported te
I've been clocking in and out of a project for a few months and now it's over.
I tagged each entry with "search", so a brief clocktable report looks like this:
#+BEGIN: clocktable :maxlevel 1 :scope file :tags t :match "search"
#+CAPTION: Clock summary at [2023-04-11 Tue 13:48]
| Tags | Headline
Hi all,
I'd like to perform some actions after a successful capture. I know
about `org-capture-.*-finalize-hook's, and I think
`org-capture-after-finalize-hook' is the one I need, but I need to
decide what action to take depending on the capture template used. How
can I access it?
TIA,
--
Mar
On 12/04/2023 10:46, Marcin Borkowski wrote:
I'd like to perform some actions after a successful capture. I know
about `org-capture-.*-finalize-hook's, and I think
`org-capture-after-finalize-hook' is the one I need, but I need to
decide what action to take depending on the capture template use
Marcin Borkowski skrev: (12 april 2023 05:46:07 CEST)
>Hi all,
>
>I'd like to perform some actions after a successful capture. I know
>about `org-capture-.*-finalize-hook's, and I think
>`org-capture-after-finalize-hook' is the one I need, but I need to
>decide what action to take depending on th
I think I even found a solution much easier solution.
Just replace each - dash with {-} when exporting latex.
In other words:
|---+-|
| Original org | New suggestion |
|---+-|
16 matches
Mail list logo
