Minor (but IMO critical) language update in documentation#150
Open
tblancher wants to merge 2 commits intotmux-plugins:masterfrom
Open
Minor (but IMO critical) language update in documentation#150tblancher wants to merge 2 commits intotmux-plugins:masterfrom
tblancher wants to merge 2 commits intotmux-plugins:masterfrom
Conversation
Author
|
Just fixed one of my filename mentions which was supposed to be in italics. The underscore |
|
lgtm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tl;dr
Changed the language of the README.md and docs/automatic_start.md:
tmux-continuumdoes NOT restore thetmuxsession on computer boot, but on user login, as far as I can tell, for both macOS and Linux.Longer explanation
I finally reread the
tmux-resurrectREADME.md, and I saw mention of thistmux-continuumpackage. I was highly intrigued, since several months ago I hacked together a goofy way to starttmuxon login.Ultimately I got it working nicely, but it was a really kludgy hack. Today I decided to break it to try and make it "better," and broke it all over again. I think I ran into the same problem as before; namely,
tmux-resurrectstarts so fast, that everyzshin my saved sessions seems to try and launch itself again; it seems there's some kind of race condition and each zsh session tries totmux new-session -As ...and I get the dreaded "sessions should be nested with care, unset $TMUX to force," which shouldn't be happening since I'm testing for the existence of${TMUX}and only trying to create/attach to the session only if it doesn't exist.After reading the
tmux-continuumREADME.md I was disheartened, since it says once enabled, starts itself on computer boot. This is actually what I don't want. Actually, in my case (at least on Linux), I'm running systemd-homed, so it really can't start on computer boot.When I started reading how this works, I discovered it's actually exactly what I want, at least on Linux, since it uses the systemd user mode. It looks the same on macOS, but there a few reasons why I won't try that there yet. Namely, my setup there is a lot more stable than Linux (since I have to use it for work), and my setup is pretty stable there already. The other reason is I don't have admin/root access to that machine (I can get it with an IT helpdesk request, but only for five minutes, and it's always a pain to request it so I'd rather not). I also hate launchd plists with a passion (XML is worse than YAML as a config file format, but they're both really effin' bad).
I actually haven't tried
tmux-continuumyet, but I thought the language saying it started on computer boot is factually incorrect, and what are we nerds if not pedantic?