Cantoraz Chou writes:
> This commit
> [[https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3502ce2dbb29b70cdbb978d144322d48cb00f26d][ox-odt:
> Fix newlines replaced by spaces in Han script]]
> brings in a strange bug.
>
> Exporting ODT produces an unexpected space inserted into each
Luca Ferrari writes:
>> 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://foo.com]]
>
> where the link is displayed without brackets, in org mode.
> I place the point at the beginning of the
Following on from thread at
https://www.reddit.com/r/orgmode/comments/zrppqw/
[First off, I just wanted to say thank you to everyone that works on
org-mode. It is a wonder.]
While I realize a few kicks at this can may have been taken, I wanted to
(re-)propose Timezone support in org-mode. The wor
Johannes Dahl writes:
> ... However, the same problem (cursor is positioned
> after closing bracket) occurs with the related commands org-shiftcontrolup and
> org-shiftcontroldown. (For completeness: in 9.6.0 they were even slightly more
> broken in that they shifted the timestamps in different d
Eppo Math writes:
> Many thanks in advance for taking the time to read this!
>
> Issue: In an org agenda block (fed to org-agenda-custom-commands), the
> number 7 passed to org-agenda-span causes the resulting block to begin
> on the first day of the week, ignoring org-agenda-start-day.
>
> Expec
Thanks for your quick response! Sorry mine took much longer ;-)
Unfortunately, I cannot confirm that this fixed the problem. I still
cannot export org-agenda-files with broken links via
org-icalendar-combine-agenda-files under Org v9.6.1, which includes the
changes of your commit.
Am 11.08.
Timm Lichte writes:
> Thanks for your quick response! Sorry mine took much longer ;-)
>
> Unfortunately, I cannot confirm that this fixed the problem. I still
> cannot export org-agenda-files with broken links via
> org-icalendar-combine-agenda-files under Org v9.6.1, which includes the
> chan
Max Nikulin writes:
>> It looks like you lost all the individual commits and commit messages in
>> the process.
>
> Ihor, it is usual merge commit of a branch with multiple commits. Cgit
> shows combined changes, but commits was not squashed. The branch started at
> dff9565c2c8bb7fe100c5278136d3
Max Nikulin writes:
> On 07/01/2023 16:04, Ihor Radchenko wrote:
>>
>> As I said, the requirement to get it into the core is re-creating
>> previous layout and bindings. The layout and bindings may be
>> customizable, but they must be available.
>
> I would say, a layout that is not worse than t
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
Daryl Manning writes:
> Following on from thread at https://www.reddit.com/r/orgmode/comments/zrppqw/
>
> [First off, I just wanted to say thank you to everyone that works on
> org-mode. It is a wonder.]
>
> While I realize a few kicks at this can may have been taken, I wanted to
> (re-)propo
On Fri, 13 Jan 2023 04:36:40 -0500 Ihor Radchenko wrote ---
> Cgit displays our bugfix merges with all the required commits.
> So, what happened what not ideal either way.
Would you like me to correct how I've incorporated my changes?
Matt writes:
> On Fri, 13 Jan 2023 04:36:40 -0500 Ihor Radchenko wrote ---
> > Cgit displays our bugfix merges with all the required commits.
> > So, what happened what not ideal either way.
>
> Would you like me to correct how I've incorporated my changes?
No. I was referring to th
Ihor Radchenko writes:
> So, the test failure is real.
The error buffer contents when the test fails is the following:
warning: using the gnuplot graphics toolkit is discouraged
The gnuplot graphics toolkit is not actively maintained and has a number
of limitations that are unlikely to be fixe
what i do is the dumb solution. c-c c-l, kill the url, c-g.
On 1/13/23, Ihor Radchenko wrote:
> Luca Ferrari writes:
>
>>> 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://foo.com]]
I had a need the other day to execute some typescript in an org document.
Now I know that there's an ob-typescript package but that doesn't quite
work the way I want and expects typescript to be installed globally (which
runs into a variety of versioning issues).
There is a better option available
* Daryl Manning [2023-01-13 11:59]:
> *Background*
>
> 1. org-time-stamp-formats TZ currently only affects display and exports
> 2. org-agenda itself is not TZ aware
> 3. Several discussions on this have taken place over time
> 4. Concerns raise included breaking backwards compatibility
>
> *Pro
sounds complex. but if timestamp syntax is to be changed, my personal
"like a broken record" view is that possibly extensible syntax could
be used, depending on the number of places ts parsing is done
currently.
i.e. on whether current ts parsing is intermingled in core org code
with ts semantics
Without wading too far into this at the moment,
timezones are an extremely tricky problem with
a whole bunch of design considerations. I am
reproducing the heading comment from laundry's
timestamp.rkt in its entirety here. Best!
Tom
https://github.com/tgbugs/laundry/blob/master/laundry/grammar/tim
I agree this is perhaps not a trivial undertaking. It really depends on the
quality of date and time libraries that exist in the lisp ecosystem. For
example, in Rust I found my timezone woes in one of my own apps were
trivial due to the chronos package, but likewise the reliance of Go
depending on
On Sat, Jan 14, 2023 at 12:51:31AM -0500, Tom Gillespie wrote:
> Without wading too far into this at the moment,
> timezones are an extremely tricky problem with
> a whole bunch of design considerations. I am
> reproducing the heading comment from laundry's
> timestamp.rkt in its entirety here. Bes
On 14/01/2023 02:06, Jean Louis wrote:
This is good for review as related to PostgreSQL database:
I agree that PostgreSQL is an example of good implementation of
time-related calculations.
https://wiki.postgresql.org/wiki/Don%27t_Do_This#Don.27t_use_timestamp_.28without_time_zone.29
I do
On 13/01/2023 22:23, Ihor Radchenko wrote:
Matt writes:
Would you like me to correct how I've incorporated my changes?
No. I was referring to the initial situation with a single commit being
displayed.
I am not sure what Max was trying to point out.
Look at the commit message for
https://g
23 matches
Mail list logo
