From: Bart Schaefer <schaefer@brasslantern.com>
To: dominik.vogt@gmx.de, zsh-users@zsh.org
Subject: Re: Bug: Losing .zsh_history
Date: Wed, 5 Oct 2022 21:34:15 -0700 [thread overview]
Message-ID: <CAH+w=7YmLcwXSj4nGFDRAOweqVvwJcSQt7SFkSTd4qmNHAZNvQ@mail.gmail.com> (raw)
In-Reply-To: <Yz4NKi/qsJc49GgX@localhost>
On Wed, Oct 5, 2022 at 4:03 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
>
> Actually, what's really strange is that the shell should not be
> started at all in this situation: The display only ever fails
> when powering on; once it works it keeps working.
It's possible that the window manager has started even though it can't
use the display, so you can't see it. Although if you normally are
presented with a login screen, that's probably not it.
Is it possible that a shell is starting on a different virtual
terminal (console)?
Incidentally, everything I've seen with publication dates in the last
7 years says that it's no longer worthwhile to worry about SSD wear
from repeated writes. Any recently-manufactured SSD will probably
outlast an HDD. I suppose you did mention that you have an old
machine, so maybe you're trying to preserve a very old drive?
next prev parent reply other threads:[~2022-10-06 4:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:55 Dominik Vogt
2022-10-05 20:01 ` Eric Cook
2022-10-05 20:20 ` Dominik Vogt
2022-10-05 21:05 ` Wesley
2022-10-05 21:24 ` Dominik Vogt
2022-10-05 22:31 ` Bart Schaefer
2022-10-05 23:03 ` Dominik Vogt
2022-10-06 4:34 ` Bart Schaefer [this message]
2022-10-06 9:40 ` Peter Stephenson
2022-10-06 10:52 ` Dominik Vogt
2022-10-06 10:30 ` Dominik Vogt
2022-10-05 20:26 ` Dominik Vogt
2022-10-05 22:16 ` Bart Schaefer
2022-10-05 22:32 ` Dominik Vogt
2022-10-06 10:31 ` Dominik Vogt
2022-10-07 11:45 ` Mikael Magnusson
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='CAH+w=7YmLcwXSj4nGFDRAOweqVvwJcSQt7SFkSTd4qmNHAZNvQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=dominik.vogt@gmx.de \
--cc=zsh-users@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).