On 12/01/2023 00:02, Ihor Radchenko wrote:
I was not, thank you. I've since pushed.
This:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4f319088ba5f11d4b6adf808f39f11dfa52c08e4
?
It looks like you lost all the individual commits and commit messages in
the process.
Ihor,
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 the current one. Org menus
may have
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.
Expected Behaviour:
Leo Butler writes:
>> So, the test failure is real.
>>
>> https://orgmode.org/list/94980226-d29a-4969-8640-1143a1979...@bundesbrandschatzamt.de
>> might be related.
>
> Ihor,
>
> How do you want to treat the patch that was included? I think we should
> have something like that to catch errors
On Wed, 7 Dec 2022 at 12:54, Ihor Radchenko wrote:
>
> Daniel Clemente writes:
>
> > Using a file with just one header:
> >
> > * something
> > :CLOCK:
> > CLOCK: [2022-12-01 Thu 17:15]--[2022-12-01 Thu 17:30] => 0:15
> > :END:
> >
> > If I put the cursor on the end timestamp (on the 3 of
Kaushal Modi writes:
> This issue is best explained with this small example.
>
> 1. Create this Org buffer:
>
> =
> #+options: author:nil toc:nil
>
> * Post 1
> :PROPERTIES:
> :EXPORT_FILE_NAME: foo
> :END:
> * Post 2
> =
>
> 2. Place the cursor at the end of :END:
> 3. C-c C-e C-s t A
Johan Bolmsjö writes:
> Org mode renders the following line in bold between the asterisks in the Emacs
> window. It seems to be the last dot after the first asterisk that triggers the
> assumed rendering bug.
>
> ┌
> │ =org-*.css= and =org-*.css.el=
> └
>
> On the other hand, the same
Matt writes:
> On Wed, 11 Jan 2023 12:02:42 -0500 Ihor Radchenko wrote ---
> > It looks like you lost all the individual commits and commit messages in
> > the process.
> >
> > Could you please revert 4f319088ba5 and re-push in such a way that
> > individual commits do appear on
On Thu, Jan 12, 2023 at 08:42:54AM +0100, Luca Ferrari wrote:
> On Tue, Dec 27, 2022 at 2:26 PM Ihor Radchenko wrote:
> >
> > Luca Ferrari writes:
> > Could you please provide more details about what is happening?
> > What exactly do you do to copy the link?
> > See
> On Jan 12, 2023, at 15:45, Luca Ferrari wrote:
>
> On Tue, Dec 27, 2022 at 2:26 PM Ihor Radchenko wrote:
>>
>> Luca Ferrari writes:
>> Could you please provide more details about what is happening?
>> What exactly do you do to copy the link?
>> See
Bastien writes:
> Kaushal, it should appear on GNU ELPA in a few hours.
Already there.
> Ihor, feel free to publish bugfix releases with no special permission
> in the future.
Noted, thanks!
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
* Samuel Wales [2023-01-12 04:07]:
> i meant bulk.
It helped! After few deviations.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
12 matches
Mail list logo
