-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #212 from budlabs/next
[FIX] #211 regex search on window properties broken
- Loading branch information
Showing
12 changed files
with
38 additions
and
64 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,43 +1,7 @@ | ||
# WE STRICT NOW | ||
### 2023.08.19 | ||
## broken regex search now works | ||
|
||
Parsing of commandline arguments are stricter | ||
for the following commands: | ||
- `i3fyra` | ||
- `i3Kornhe` | ||
- `i3viwiz` | ||
- `i3flip` | ||
fix for issue #211 . | ||
Big thanks to @henryzxb for reporting | ||
|
||
The change is related to the issue (#183). | ||
Before this patch f.i. the command: `i3flip perv` | ||
was valid and would flip the focus in the *previous* direction. | ||
Because only the first character in the argument was used. | ||
|
||
Now this will result in an error: `perv` is not a valid direction. | ||
Valid directions for this case would be "prev, p, previous". | ||
Arguments are still case insensitive. | ||
|
||
--- | ||
|
||
A bugfix in `i3king` on the same theme is that, previously | ||
it was possible to define a rule without a command (probably because of a typo/mistake: #207), | ||
and this could lead to unpredictable bad behaviour and issues. | ||
**Now** if a rule is defined without a command, it will be ignored | ||
and proper error messages will be printed. | ||
|
||
--- | ||
|
||
I also fixed the bug related to workspace name of | ||
i3fyra workspace for the 42'nd time. | ||
|
||
--- | ||
|
||
Finally a minor printf debugging improvement where | ||
arguments to `--json` (usually a full `i3-msg -t | ||
get_tree` string) is now replaced with `...` in | ||
debugging stderr output. | ||
|
||
--- | ||
|
||
big thanks to @gmardom and @1ntronaut for reporting | ||
and helping to troublehsoot the issues! | ||
Allthough small, this change affects all i3ass commands, | ||
except i3king. Hopefully we didn't break something. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
## broken regex search now works | ||
|
||
fix for issue #211 . | ||
Big thanks to @henryzxb for reporting | ||
|
||
Allthough small, this change affects all i3ass commands, | ||
except i3king. Hopefully we didn't break something. |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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