From: Christopher Miles <firstname.lastname@example.org> To: Maxim Nikulin <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com> Subject: [PATCH] Re: [BUG] [C-u C-u C-c C-o] open link with external program invalid to open file Date: Thu, 21 Jan 2021 00:58:27 +0000 [thread overview] Message-ID: <PAXPR08MB664030A7DFC89FF2AFD93CFBA3A10@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1080 bytes --] Maxim Nikulin <email@example.com> writes: > I have realized that :filter argument is not appropriate to arbitrary > handler that could spam with various assert messages. Maybe :sentinel is > better to report configuration problem to user when handler is called > with inappropriate arguments. Yes, use ~:sentinel~ is better for report problem when detect process failed or configuration error. ~:filter~ usually used in handling process output. I "=git am=" your first patch, but failed to apply your second patch. Seems not continuous. So I modify code manually. I found I can't find the local variable ~shell-command~, and ~shell-command-switch~. Can your provide complete patch? So I can test it. I update subject to prefix with [PATCH] so that reader knows this thread is on patch discussion. -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-21 1:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-13 7:49 stardiviner 2020-06-13 14:51 ` Nicolas Goaziou 2020-06-14 9:08 ` stardiviner 2020-06-14 21:06 ` Nicolas Goaziou 2021-01-10 11:26 ` [BUG] [C-u C-u C-c C-o] open link with external program auto exited before child process " Christopher Miles [not found] ` <87sg799gnx.fsf@numbchild> 2021-01-10 12:13 ` Christopher Miles 2020-09-05 7:52 ` [BUG] [C-u C-u C-c C-o] open link with external program invalid to " Bastien 2021-01-18 16:32 ` Maxim Nikulin 2021-01-19 1:53 ` Christopher Miles 2021-01-19 17:00 ` Maxim Nikulin 2021-01-20 3:21 ` Christopher Miles 2021-01-20 16:27 ` Maxim Nikulin 2021-01-21 0:58 ` Christopher Miles [this message] 2021-01-21 17:12 ` [PATCH] " Maxim Nikulin 2021-01-22 6:00 ` Christopher Miles 2021-03-10 14:55 ` Maxim Nikulin 2021-03-11 9:33 ` Christopher Miles
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style 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=PAXPR08MB664030A7DFC89FF2AFD93CFBA3A10@PAXPR08MB6640.eurprd08.prod.outlook.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='[PATCH] Re: [BUG] [C-u C-u C-c C-o] open link with external program invalid to open file' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).