From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 51132@debbugs.gnu.org
Subject: bug#51132: Make sure user is doubly aware of finished complilations
Date: Wed, 20 Oct 2021 08:09:35 +0200 [thread overview]
Message-ID: <87ilxs1b34.fsf@gmail.com> (raw)
In-Reply-To: <87tuhcijs0.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Wed, 20 Oct 2021 09:09:51 +0800")
積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
> Maybe (info "(emacs) Compilation") should mention:
> "Like KLG says, it is extremely easy to forget you had a lengthy compile
> job running, and ...
>
> KLG> 5. consider I have finished working on the unrelated matters, and close
> KLG> Emacs,
>
> KLG> 6. bang my head on the desk out of frustration and self-loathing.
>
> ... therefore perhaps consider wrapping your compile jobs in a nohup(1)
> statement, perhaps with a tail -f nohup.out to simulate traditional
> compile-mode output. Example: ..."
That, or maybe advertise compilation-finish-functions more? Promote it
to a defcustom, keep it nil by default, add some :options, such as:
- a function that calls notifications-notify,
- a function that saves the buffer; serving suggestion:
(defun compilation-save-buffer (buffer _results)
;; TODO:
;; - better path-separator escaping?
;; - give user more control over directory?
;; - give user more control over filename?
;; - use write-file and mark buffer as "unsaved"?
(let* ((cmd (string-replace "/" "-"
(with-current-buffer buffer compile-command)))
(time (format-time-string "%F-%T")))
(with-current-buffer buffer
(write-region (point-min) (point-max) (format "%s-%s.log" time cmd)))))
… and document it in (info "(emacs) Compilation").
I wouldn't mind working on a patch, if the above sounds appealing. I'm
a bit swamped these days, but from our discussion I understand that this
wouldn't exactly be a high-priority feature anyway :)
next prev parent reply other threads:[~2021-10-20 6:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 6:50 bug#51132: Make sure user is doubly aware of finished complilations 積丹尼 Dan Jacobson
2021-10-11 8:46 ` Lars Ingebrigtsen
2021-10-11 9:21 ` Kévin Le Gouguec
2021-10-11 14:44 ` bug#51132: [External] : " Drew Adams
2021-10-11 16:03 ` Eli Zaretskii
2021-10-11 16:21 ` Drew Adams
2021-10-11 16:31 ` Eli Zaretskii
2021-10-11 16:44 ` Drew Adams
2021-10-12 8:01 ` 積丹尼 Dan Jacobson
2021-10-12 13:59 ` Eli Zaretskii
2021-10-11 14:41 ` Drew Adams
2021-10-11 16:03 ` Eli Zaretskii
2021-10-11 16:13 ` Drew Adams
2021-10-11 12:16 ` Eli Zaretskii
2021-10-12 8:04 ` 積丹尼 Dan Jacobson
2021-10-12 14:00 ` Eli Zaretskii
2021-10-12 15:16 ` Kévin Le Gouguec
2021-10-12 16:11 ` Eli Zaretskii
2021-10-12 18:24 ` Kévin Le Gouguec
2021-10-20 1:09 ` 積丹尼 Dan Jacobson
2021-10-20 6:09 ` Kévin Le Gouguec [this message]
2021-10-22 12:32 ` 積丹尼 Dan Jacobson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilxs1b34.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=51132@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.