Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

Hi, Ihor, Sorry for the delay with fixes, took some time before I got time to finish this. Thanks for your review and looking forward for the next iteration. See new version in the attachment. Comments are inline. Ihor Radchenko writes: > Mikhail Skorzhisnkii writes: > >&g

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

into separate commit • More grammar and wording fixes in changelogs Thanks, Mikhail Ihor Radchenko writes: > Mikhail Skorzhisnkii writes: > >>> Also, what will happen in a file like >>> >>> #+TITLE: Begin title >>> #+TITLE: .. end title >

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

Resubmitting this patch with better commit message. Mikhail Skorzhisnkii writes: > I have signed FSF papers. Attaching a rebased patch with additional changes to > ORG-NEWS > > Ihor Radchenko writes: > >> “Mikhail Skorzhinskiy” writes: >> >>> Thanks for r

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

Thanks for your comment, Ihor. I have addressed your comments, see some comments inline. Attaching new version of the patch. Ihor Radchenko writes: > Mikhail Skorzhisnkii writes: > >> I have signed FSF papers. Attaching a rebased patch with additional changes >> to >

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

Ah, sorry — probably forgot to attach it, yes. See the second patch here in the attachment. Ihor Radchenko writes: > Mikhail Skorzhisnkii writes: > >> Subject: [PATCH 1/2] org-agenda.el: customize outline path in echo area > > I do not see the second patch. Did you forget t

Re: [PATCH] org-agenda.el: customise outline path in echo area

I have signed the FSF papers now and we can continue the review of this work now. I am attaching updated and rebased patch for this and another e-mail thread, since these two patches are depend on each other. I have additionally tested the functionality of these changes by verifying that it

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

I have signed FSF papers. Attaching a rebased patch with additional changes to ORG-NEWS Ihor Radchenko writes: > “Mikhail Skorzhinskiy” writes: > >> Thanks for review, Ihor. I have sent a copyright assignment request. Will >> resubmit the patches as soon as I complete the process. > > Thanks!

Re: [PATCH] org-refile.el: show refile targets with doc. title

I have signed the FSF papers. However for the simplicity I will send renewed patch in different thread. You may consider this thread to be closed.q E-Mail thread I am going to use is: Thanks, Mikhail

Re: [PATCH] org-agenda.el: agenda*: add lost argument

This patch is no longer needed, as the bug was fixed in other commit. Ihor Radchenko writes: > Mikhail Skorzhinskii writes: > >> * lisp/org-agenda.el (org-agenda): add lost argument for agenda* > > Thanks! I am not able to apply your patch onto main. Could you resend, > preferably adding the

Re: Bug: Entries with 0 minutes logged triggers clocking overlap [9.5 (nil @ /home/eddie/.emacs.d/.local/straight/build-26.3/org-mode/)]

Hi, Eddie, I am not against fixing clocking overlap, however I personally deal with this by not clocking zero time at all. Are you aware about the existence of `org-clock-out-remove-zero-time-clocks'? Setting this variable to non-nil will remove clock lines when the resulting time is zero.

Re: [org-save-all-org-buffers] Saving is not reliable?

ch or make an org operation require two undos. the agenda is one place where these bugs have existed. On 12/9/20, Eric S Fraga wrote: On Wednesday, 9 Dec 2020 at 11:16, Mikhail Skorzhisnkii wrote: It's kind of reproduction scenario. Basically I need to modify buffer from search-t

Re: [org-save-all-org-buffers] Saving is not reliable?

efore save-buffer-always activate) "always save buffer" (set-buffer-modified-p t)) It looks like it helps me. I'll report back to this thread when I find the offender. I guess I'm calling (set-buffer-modified-p nil) somewhere unknowingly. Mikhail Skorzhinskii Kyle Meyer writes:

[org-save-all-org-buffers] Saving is not reliable?

Hello forum, I start noticing some time ago that saving org-mode buffers works unreliably in my setup. Most of the time I am using function `org-save-all-org-buffers' from core org. Unfortunately I don't have a good reproduction scenarios of this bug. In fact I don't have reproduction scenario at

Re: generate an org file for today's appointments

I'd suggest to use function "org-agenda-write". You can export your agenda views to org files too! However, the formatting will be different. Probably something like: * Event A SCHEDULED: <2020-12-03 Thu 10:00-12:00> * Event B SCHEDULED: <2020-12-03 Thu 10:00-11:00> * Event C SCHEDULED:

Re: Clock tables and two ways to categorize tasks

Hi Marcin, I tried to solve this issue for myself. My first attempt to solve it was to understand which tags are interesting and then make a template with as many tables as there were interesting tag combinations. But then I faced another problem: sometimes I am using different set of tags

Re: Folding headings which contain only blank lines

Hi, Patch ee3c3b554799c9f0fbe387848cd9eec7e9ab9d95 breaks unfolding when org-cycle-separator-lines set to -1. How to reproduce: 1. Set org-cycle-separator-lines to -1; 2. Try to fold and then unfold "Test" in the following file: #+begin_example ,* Test 1 ,** Test 2 ,* Test 3