From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ihor Radchenko Subject: Re: Emacs bug 37890; killing capture buffer Date: Wed, 18 Dec 2019 10:16:22 +0800 Message-ID: <87sgliz8cp.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> References: <87r217lwwz.fsf@web.de> <874ky3sdhs.fsf@alphapapa.net> <87woaxw79i.fsf@web.de> <8736dj27wn.fsf@web.de> <87mubqrgue.fsf@alphapapa.net> <87v9qedd4f.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42496) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ihOv5-0001CA-RG for emacs-orgmode@gnu.org; Tue, 17 Dec 2019 21:18:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ihOv4-000811-Lk for emacs-orgmode@gnu.org; Tue, 17 Dec 2019 21:18:35 -0500 Received: from mail-yw1-xc35.google.com ([2607:f8b0:4864:20::c35]:34505) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ihOv4-0007xN-Er for emacs-orgmode@gnu.org; Tue, 17 Dec 2019 21:18:34 -0500 Received: by mail-yw1-xc35.google.com with SMTP id b186so234099ywc.1 for ; Tue, 17 Dec 2019 18:18:34 -0800 (PST) In-Reply-To: <87v9qedd4f.fsf@web.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Michael Heerdegen , Adam Porter Cc: emacs-orgmode@gnu.org Dear Michael, > BTW, what is the canonical place to report org-mode bugs? Emacs bug > reports are not (takes a long time until someone even notices) -- I > thought this list would be good...or is there a better place? @Adam > it's ok if you answer, though I'm a bit disappointed that no one else > seems to care so far... You can try M-x org-submit-bug-report ;) Then it becomes clear that you are in the right place already. Best, Ihor Michael Heerdegen writes: > Adam Porter writes: > >> I guess you're asking me, since I'm the only other person in this >> thread--but I'm not an Org maintainer, so my opinion isn't very >> important. IMO, the hooks are worth considering, however they should be >> done very, very carefully, because bad things can happen when functions >> called in kill hooks don't work as expected (e.g. they can make it very >> difficult to kill a buffer or the Emacs process, especially for an >> average user). > > Yes, all true. I didn't even check if the code I posted breaks any org > commands that kill the buffer. So far it's only meant for demonstration > (and my personal usage). > > Will my request be noticed here, or do you think I should report it to > some other place? > >> > BTW, what about my question whether my original bug report can be >> > closed? >> >> I haven't seen your bug report. Was there discussion about it >> previously? > > No, no discussion at all. As I said, it is Emacs bug #37890, this was > my issue: > > | I want to capture an APPT with `org-capture'. I the pop-up buffer to > | edit the item I move the date to the second line and add text after the > | date (personal preference). That loses the final newline in > | CAPTURE-todo.org. As a result, the headline of the item following the > | item to be inserted gets appended to the last line of the text: > | > | ** APPT Abc > | <2019-10-23 Mi> > | text... ** APPT 8:30 Important Appointment > | > | breaking the whole item. The user should somehow be prevented from that > | happening. > > It seems it has been resolved, just without noticing my bug report. If > you can confirm that the cited issue has been cared about, I'll close it > as done. > > BTW, what is the canonical place to report org-mode bugs? Emacs bug > reports are not (takes a long time until someone even notices) -- I > thought this list would be good...or is there a better place? @Adam > it's ok if you answer, though I'm a bit disappointed that no one else > seems to care so far... > > > Thanks, > > Michael. >