emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Bhavin Gandhi <bhavin7392@gmail.com>, Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-auto-repeat-maybe: error "Can’t expand minibuffer to full frame" and missing log note
Date: Wed, 17 Aug 2022 17:45:19 +0800	[thread overview]
Message-ID: <878rnn19w0.fsf@localhost> (raw)
In-Reply-To: <CAOn=hbcg8ZvGRBLXfNJYtzdXdjsG+qes7ovw8jEBP9Xxt_a6eA@mail.gmail.com>

Bhavin Gandhi <bhavin7392@gmail.com> writes:

>> Thanks! I received the PDF to sign the next day after my email, this
>> will probably take a couple of days more from my side as I'm talking
>> with my employer.
> I finally got this done. I now have a fully executed copy of the copyright
> assignment (signed by FSF and me). Do I need to send it to someone so
> that they can check and update the page at
> https://orgmode.org/worg/contributors.html ?

You do not need to share the paperwork with us. FSF has a database
available to GNU maintainers with a list of all the people with
copyright assignment.

I am CCing Bastien.
Bastien, can you please confirm that Bhavin's paperwork is registered
and add him to the contributor list?

>> Yikes! Then, can also check for window-minibuffer-p, but I feel that it
>> will be a fight against all kinds of edge cases.
> I haven't been able to make much progress on this bug in the last two
> weeks. Will try to send a patch in a few days, as the steps I gave above
> feels like an edge case which we won't see happening hopefully.

Your patch will be already an improvement.

I guess that the proper fix of this type of issues would be rewriting
the note system in such a way that it uses recursive editing. Then, we
can make the user write the note in the middle of a running command and
not worry about post-command-hook quirks. But that will be a much more
involved change.

Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

  reply	other threads:[~2022-08-17  9:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 15:48 Org Agenda Error Michael Powe
2022-06-12 17:46 ` Bhavin Gandhi
2022-06-13  3:29   ` Michael Powe
2022-06-13 17:31   ` Bhavin Gandhi
2022-06-18 18:00     ` [BUG] org-auto-repeat-maybe: error "Can’t expand minibuffer to full frame" and missing log note Bhavin Gandhi
2022-07-01  2:14       ` Ihor Radchenko
2022-07-03 17:10         ` Bhavin Gandhi
2022-07-04 12:03           ` Ihor Radchenko
2022-07-10 17:23             ` Bhavin Gandhi
2022-07-11  1:57               ` Ihor Radchenko
2022-07-14 15:22                 ` Bhavin Gandhi
2022-07-16  9:21                   ` Ihor Radchenko
2022-07-21 18:03                     ` Bhavin Gandhi
2022-07-26 11:49                       ` Ihor Radchenko
2022-08-16 18:17                         ` Bhavin Gandhi
2022-08-17  9:45                           ` Ihor Radchenko [this message]
2022-09-01  9:48                             ` Bastien Guerry
2022-09-25 18:16                             ` Bhavin Gandhi
2022-09-26 12:46                               ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rnn19w0.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=bhavin7392@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).