| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
Update actions versions and ingore existing PyPI versions
|
|/
|
|
|
|
|
|
|
|
| |
The actions checkout and setup-python have never versions and there is
currently an issue with uploading to PyPI (see #52).
This ups the versions for the GitHub Actions and lets the publish to
PyPI action skip existing versions since the cannot be changed after
publishing. See
https://github.com/pypa/gh-action-pypi-publish#tolerating-release-package-file-duplicates
|
| |
|
| |
|
|\
| |
| | |
Split out argparse.ArgumentParser into its own function
|
|/
|
|
| |
This is useful for use with argcomplete or argparse-manpage
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
split ratio, split horizontal factor, split vert factor
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Forgot to change file_path variable name
|
|/ / |
|
|\ \
| | |
| | | |
Refactor autotiling argparse setup for conciseness
|
|/| |
| | |
| | | |
Refactor autotiling argparse setup for conciseness
|
|/ /
| |
| |
| |
| | |
- Utilized f-strings for improved readability and string formatting.
- Removed redundant line breaks and aligned argument definitions.
- Consolidated file handling with context managers for better error resilience.
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Add option to limit to outputs
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Apparently there are differences in the returned ipc_data for sway and
we cannot use the ipc_data of the event that triggered the handler.
To accommodate this, we look at the currently focused container and
check its parents recursively until we find the output.
|
|/ /
| |
| |
| |
| | |
To enable different limits on different outputs, you can start two
processes and limit them to the outputs you want.
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Add depth limit as argument for how often to autotile
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The help and README did not go into details what exactly the --limit
option does.
Since it can be used to imitate a master-stack layout, and can enable
tabbed or stacking layouts to some degree, this adds the explanation in
the section talking about this limitation.
It softens the limitations of autotiling while still stressing that
tabbed and stacked layouts may behave unexpectedly and are not supported
by autotiling.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With lots of splits the hierarchy can get deeper than normal, if
containers get closed. i3 does not flatten this hierarchy (atm).
This means that the depth option does needs to ignore containers that
only contain one child/node. This is done only incrementing the current
depth when checking against the limit if the nodes of the parent
container is bigger than 1.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the script will autotile (vsplit/hsplit) every window focused
on with no limit.
At a certain depth this behaviour is not desirably to me and I want to
add more windows to the same container. Especially for terminals I
prefer to have more space horizontally than vertically to see the entire
line if possible.
To achieve this, I add a optional parameter to prevent further
autotiling after the specified limit. For example with a 16:9 display
and a depth limit of 1, it will split horizontally first and then only
split vertically but in the same container.
```
________________
| | |
|--------| |
| |-------|
|--------| |
|________|_______|
```
As a side effect, this enables stacking and tabbed layouts after
reaching the limit.
The default behavior is still the same with an infinite limit for how
deep to autotile.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Add publish to PYPI workflow
|
|/ |
|
|\
| |
| | |
refactor: move `is_full_screen` outside if statement
|
|/
|
|
| |
`is_full_screen` was being set to the same value in both branches
|
| |
|
| |
|
|\
| |
| | |
Allow choosing events to subscribe
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Fixed manually switching between layouts not working
|