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

Add config option record_history #917

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MyNameIsCosmo
Copy link
Contributor

Fixes #909

This PR keeps the bspc wm -h <true/false> command, which now changes the record_history config value.

Additionally, you can call bspc config record_history <true/false> to toggle history recording.

@@ -1812,6 +1813,7 @@ void get_setting(coordinates_t loc, char *name, FILE* rsp)
GET_BOOL(remove_disabled_monitors)
GET_BOOL(remove_unplugged_monitors)
GET_BOOL(merge_overlapping_monitors)
GET_BOOL(record_history)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are using spaces for indentation here

Suggested change
GET_BOOL(record_history)
GET_BOOL(record_history)

@@ -992,7 +992,7 @@ Manage all the unmanaged windows remaining from a previous session\&.
.PP
\fB\-h\fR, \fB\-\-record\-history\fR on|off
.RS 4
Enable or disable the recording of node focus history\&.
Copy link
Contributor

@emanuele6 emanuele6 Sep 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should edit the asciidoc file, not the man page directly: this change will be overwritten when the man page is recompiled with make doc.

@emanuele6
Copy link
Contributor

emanuele6 commented Sep 6, 2020

What's the point of this patch?
I guess it allows you to know if the history is being recorded with bspc config record_history, since it isn't currently possible to know if the history is being recorded: neither with bspc wm -h nor by parsing the output of bspc wm -d.

But what is the point of having both wm -h and the record_history setting?

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

Successfully merging this pull request may close these issues.

Config option for ignore_history from bspc wm -h flag
2 participants