From: Samuel Wales <samologist@gmail.com>
To: James Thomas <jimjoe@gmx.net>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: can shell mode keep a log?
Date: Sat, 10 Sep 2022 19:08:44 -0700 [thread overview]
Message-ID: <CAJcAo8s601K_LtyosOa0XuzhtanNxN_iqMcf+p5iG0f3QyDkMg@mail.gmail.com> (raw)
In-Reply-To: <87a677n8dw.fsf@gmx.net>
comint scrolls off top. would auto save mode take that into account?
idk about shell-mode-hook, but i was thinking
comint-preoutput-filter-functions would maybe allow saving each set of
output [idk if per chunk of output or per prompt pair], but this
definitely seems like a feature only i need. :/
On 9/9/22, James Thomas <jimjoe@gmx.net> wrote:
> Samuel Wales wrote:
>
>> i need ti to be automatic, for the entire shell session, for all
>> comand including prompts, sort of like typescrpt ut that would likely
>> have issues i am unware of such as commands outputtig to termianl or
>> osehting.
>
> You can enable auto-save-mode in the shell buffer. Make sure to read the
> manual about the options to control its application.
>
>> soign write-file is good for manual saves and i should remember it
>> morel although i think that changes the visited filename or so. but
>> it is not the automatic solution i am looking or. i want a log of the
>> session.
>
> Once you use write-file, from then on, auto-save-mode is enabled in it
> by default.
>
>> iow a complete history o the shell sessions in my shell buffers, saved
>> continuously or continually to files efficiently.
>
> You can probably use shell-mode-hook to do one of the above in all such
> buffers.
>
> --
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
prev parent reply other threads:[~2022-09-11 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 5:02 can shell mode keep a log? Samuel Wales
2022-09-07 5:26 ` Jude DaShiell
2022-09-07 5:43 ` Emanuel Berg
2022-09-07 17:12 ` Philip Kaludercic
2022-09-07 18:23 ` Eli Zaretskii
2022-09-08 0:40 ` Samuel Wales
2022-09-08 0:59 ` Emanuel Berg
2022-09-10 4:47 ` James Thomas
2022-09-11 2:08 ` Samuel Wales [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJcAo8s601K_LtyosOa0XuzhtanNxN_iqMcf+p5iG0f3QyDkMg@mail.gmail.com \
--to=samologist@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=jimjoe@gmx.net \
/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.
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).