Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

capture screen does not work #22

Open
pinggit opened this issue Feb 18, 2018 · 4 comments
Open

capture screen does not work #22

pinggit opened this issue Feb 18, 2018 · 4 comments

Comments

@pinggit
Copy link

pinggit commented Feb 18, 2018

I configured:
set -g @screen-capture-path '$HOME/tmux-logs'

and when I press prefix-alt-p, I do see:
'Screen capture saved to $HOME/tmux-logs/tmux-screen-capture-work-2-1-20180218T115701.log'

but, I can not find that file.

wired that I remember I saw it once, but under home folder, but after I remove it, I never see screen capture files anywhere...

@bedge
Copy link

bedge commented May 25, 2019

I'm trying to set the same thing. The command you're using doesn't seem to have any affect.

After executing:

set -g @screen-capture-path '$HOME/logs/tmux'

Then hitting & alt-shift-p, I see:

History saved to /Users/bedge/tmux-history-a-infor-1-1-20190525T075004.log

I'd also like to know what variable I need to set to change this.

@Kr1ss-XD
Copy link

Kr1ss-XD commented May 25, 2019

I think I can help here.

Since you both used single quotes, the $HOME variable is not being expanded, i.e. the file is written to $HOME/logs/tmux -relative to your current working directory-, rather than to /home/<username>/logs/tmux, what you probably want it to.

So you should be fine if you omit the single quotes or (better !) replace them with double quotes.

EDIT : @bedge - btw, just noticed that you pressed the key combination for save-complete-history, but the path you were setting is for screen-capture. The default combination for this is alt+p (without shift).

@bedge
Copy link

bedge commented May 25, 2019

I looked into this more, and the start_logging doesn't source the variable.sh. So it's not apparently intended to be called directly.
I addressed this in my PR.

...and, yes, the single quotes were a problem 👍

@KorpoleRithika0x1
Copy link

we should close this issue now Ig

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants