xbc5 / awesome Goto Github PK

Create one for dev (webdev/webext) and normal.

You will need to investigate the potential use of Vim modes first (#12).

Send clients without explicit designation to the default workspace. This allows the user to combine tags without the clutter.

Create a distinct binding for each layout, in contrast to cycling through them.

matrix, dev browsers, daily/youtube browsers, nvim (IDE), templates, bookmark windows (on their own workspace), test..

Manually jump the cursor to a specific place on the screen. This is useful when using a keyboard mouse, and makes finding the cursor easier by jumping it to a specific location.

You can do it with xdtool mousemove <<X>> <<Y>>, but you will have to calculate positions from screen size (do this every time so that it's responsive to screen size changed -- like moving to another monitor).

Tags implicitly select the current workspace, change this so that the user has to explicitly select workspaces. This makes joining tags less confusing, because you first have to change to that tag before combinign it with another.

e.g. not: [change to A] => [select B] => combined
instead: [select A] => [select b] => combined

Create a shell prompt that uses FZF to search through shell history with a frecency algorithm. If the user selects no matches, but instead hits enter for the current line, then execute that command. Also, execute automatically any historical commands chosen.

It might be worth making this a standalone project.

For items that are not tags or window placeholders (i.e. the typical taskbar).

Instead of using those sliding floating windows, display them in a taskbar (#16). This could be a different taskbar to the one that contains tags (screens) and window placeholders (i.e. the typical taskbar); you could use a dedicated taskbar for both notifications and running VMs (#14).

The notification itself should appear as a single row of text, which collapses into a small icon after 10 seconds. If another notification appears, if will collapse the current one. An icon with a number (of notifications) should live permanently on the taskbar, when the user activates a keyboard shortcut (#15), a sliding side window (#17) should open, displaying all notifications as a list. This list is browsable, and the user can expand, or delete items with vim key bindings.

Display the names of running VMs in a dedicated taskbar (#16); when the user activates a keymap (#15) then display more details in a sliding side window (#17).

e.g. vim modes. Consider insert, normal, and visual select modes.

• insert mode: interact (input) with the currently selected window;
• normal mode: manage the current window (layout);
• visual mode: select windows on a window by window basis (i.e. not block select) so that the user can execute commands (e.g. move) on them;

Make the current mode highly visible -- much more visible than Vim.

To display various contexts -- for example running VMs (#14). This window should display on keymap activation (#12), and slide in from the right.

Simple start scripts can be user unit files. This is a chore to make for every one, but the (oneshot) unit file is the same in almost every case.

This can probably be a standalone project (in fact it's probably best that it is); it does not need to be complex, just a simple shell script with an FZF interface.

• create a popup (floating) interface that will fuzzy select an executable file from $PATH, and create, enable, and start a unit file for it;
• create a means to start, stop, disable, enable any unit file;
• create a means to create a fully customisable unit file, such that when oneshot isn't sufficient, it will open your $EDITOR | vim with a cookie-cutter unit file already populated; when the user "saves", it's saved to a local systemd unit directory; when the user exits, it will enable and start the unit file;

Right now, if you switch away from a tag combination it is lost. Allow users to easily create custom tag combinations. Analogous to register in Vim, provide a feature that users can quickly an ephemerally bind custom tag combinations to a key.

Possibly related to #11 and #12.

e.g. dev:browser -- add it to the items within the taskbar, and remove the other useless text.

This means think about the keymaps, and diagram them first. Consider the most used bindings and put them on the home row.

e.g. . Use the currently selected domain as the context.