profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/stevensonmt/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

fzingg/hyperloop-showcase 4

A simple Rails 5.0.1 app showcasing HyperReact, HyperMesh, Opal and associated technologies

stevensonmt/Arc-Gruvbox 4

Arc GTK theme adapte to use the Gruvbox color scheme

stevensonmt/earthy 2

gtk3.0 theme based on Nordic with color palette derived from gruvbox

stevensonmt/elmup 2

Very simple CLI tool for updating dependencies in your elm app. No safety guarantees but a backup is made of your elm.json so reversion should be simple.

stevensonmt/binfiles 0

various scripts

stevensonmt/DynCSS 0

Dynamic CSS Rules

stevensonmt/elm 0

Source companion for the Elmlang course at

startedunbalancedparentheses/spawnedshelter

started time in 2 days

pull request commentleftwm/leftwm

Add 'max_window_width' feature

I agree that this is a pretty niche feature, that's why we should keep the feature as basic as possible for now. But a lot of WMs aren't really ultra-wide monitor friendly without requiring custom patches, I hope this can make LeftWM stand out a bit in that regard. :)

FWIW the ability to define workspaces already makes leftwm a good tool for ultra wide monitors. This feature does make it more flexible and user friendly, though.

hertg

comment created time in 2 days

pull request commentleftwm/leftwm

Add 'max_window_width' feature

Would it be feasible to create additional layouts that take the max_width setting from config.toml? This would make it easy to sort of toggle the feature on off by having both Monocle and MonocleMaxWidth enabled.

I'm not sure if creating completely separate layouts for this is better than applying the config to the existing ones, it would lead to a lot of duplicate code. If toggling the max-width feature is something people want in the future, there probably is a more user-friendly approach to achieve that than having to switch layouts.

Fair enough. I don't think it would have to be duplicate code necessarily. The max_width variants could call the regular variants but passing different dimension parameters based on the max width setting. In any case it looks like this is going to work in the paradigm you've already started so I won't belabor the issue. Cool feature.

hertg

comment created time in 3 days

pull request commentleftwm/leftwm

Add 'max_window_width' feature

Sorry, I should have clarified, Monocle was simply an example. It would mean adding layout enum variants for each layout you want a max_width option enabled.

hertg

comment created time in 3 days

pull request commentleftwm/leftwm

Add 'max_window_width' feature

I like this feature a lot and the code looks great. Conceptually though this seems like a different set of layouts rather than a setting for a window or workspace. Would it be feasible to create additional layouts that take the max_width setting from config.toml? This would make it easy to sort of toggle the feature on off by having both Monocle and MonocleMaxWidth enabled.

hertg

comment created time in 4 days

startedRashad-707/rhombuses

started time in 5 days

push eventstevensonmt/earthy

Matthew Stevenson

commit sha 51fdae40f8f31a384c225e0d66de39c23c1d48c1

remove unnecessary assets

view details

push time in 17 days

push eventstevensonmt/earthy

Matthew Stevenson

commit sha f9b1241e98d921ee5eb4c165b3cacf1d0caa8991

add assets, unedited from Nordic

view details

push time in 17 days

issue commentleftwm/leftwm

I can't open more than three terminal emulators in a single workspace

I wonder if your GPU type/driver/config is maybe part of the issue since alacritty makes use of GPU processing.

amarakon

comment created time in 18 days

issue closedelixir-lsp/elixir-ls

Vim error: Error:elixir-ls: ElixirLS has crashed. See Output panel.

Environment

  • Elixir & Erlang versions (elixir --version): Elixir 1.12.2 (compiled with Erlang/OTP 24)
  • Operating system: Manjaro Linux kernel 5.10.60-1
  • Editor or IDE name (e.g. Emacs/VSCode): VIM 8.2
  • Editor Plugin/LSP Client name: ALE

Error:elixir-ls: ElixirLS has crashed. See Output panel. I get this error every time a .ex file is opened in a new buffer or written to a buffer in vim. Created a new Mix project with mix new empty and had the same issue.

closed time in 22 days

stevensonmt

issue commentelixir-lsp/elixir-ls

Vim error: Error:elixir-ls: ElixirLS has crashed. See Output panel.

nevermind. just had to recompile to v 0.8.

stevensonmt

comment created time in 22 days

issue openedelixir-lsp/elixir-ls

Vim error: Error:elixir-ls: ElixirLS has crashed. See Output panel.

Environment

  • Elixir & Erlang versions (elixir --version): Elixir 1.12.2 (compiled with Erlang/OTP 24)
  • Operating system: Manjaro Linux kernel 5.10.60-1
  • Editor or IDE name (e.g. Emacs/VSCode): VIM 8.2
  • Editor Plugin/LSP Client name: ALE

Error:elixir-ls: ElixirLS has crashed. See Output panel. I get this error every time a .ex file is opened in a new buffer or written to a buffer in vim. Created a new Mix project with mix new empty and had the same issue.

created time in 22 days

starteddenofn/svelte

started time in 25 days

startedLitarvan/lightdm-webkit-theme-litarvan

started time in a month

delete branch stevensonmt/leftwm

delete branch : leftwm-check_for_theme

delete time in a month

issue commentleftwm/leftwm

wayland support

Am I correct that leftwm is architected to allow implementation of other backends via implementing the display_server traits for that backend? Are there other places where X11 specific code lives?

bijang

comment created time in a month

issue commentleftwm/leftwm

Random freezing issues, hard to troubleshoot

I'm using this picom fork from AUR which has rounded corners and the dual kawase blur. I haven't had any issues with it, but not sure if picom is likely to be the source of your problem. If picom crashed you would expect just to not have compositor features like transparency and shadows rather than a total freeze.

JacobHin2

comment created time in a month

GollumEvent

issue commentleftwm/leftwm

LeftWM crushed for dropdown terminal

can you post the contents of up and your current config.toml here? Are you sure leftwm is crashed? You might have a black screen if you aren't running any sort of background/wallpaper application like feh.

kazi-sifat-plus9a

comment created time in a month

issue commentleftwm/leftwm

LeftWM crushed for dropdown terminal

The location of your config file is fine. Are you able to open tilda without launching it from your up script? Can you post your up script file? @VuiMuich is probably correct that configuring a scratchpad is probably the fix. Alternatively you might work around this if you're using polybar by implementing a configuration like seen here.

kazi-sifat-plus9a

comment created time in a month

pull request commentleftwm/leftwm

Partial liquid templates resolve #439

Once this is merged and part of a release I can update the config wiki. Just making this comment to remind myself.

stevensonmt

comment created time in a month

pull request commentVuiMuich/leftwm

refactor theme check

So the find_config_files method is not working the way I thought. The iterator is just a single item with the config path ending in "current" rather than returning an iterator over the files in that directory. It looks like xdg::BaseDirectories::list_config_files is what I needed instead. Check most recent commit to see if it works for you. Worked for me.

stevensonmt

comment created time in a month

push eventstevensonmt/leftwm

Matthew Stevenson

commit sha 84a546ae4b67d31b733c2f184e8193f74c2ef737

use list_config_files not find_config_files

view details

push time in a month

PR opened VuiMuich/leftwm

refactor theme check

@VuiMuich, what do you think of this approach? I haven't tested it to see if the xdg::BaseDirectories::find_config_files() works the way I think it does, but it seems like it should.

+84 -67

0 comment

1 changed file

pr created time in a month

create barnchstevensonmt/leftwm

branch : leftwm-check_for_theme

created branch time in a month

pull request commentleftwm/leftwm

Layout Per Tag

Maybe this is not a configurable setting at all but a command that takes a layout plus a workspace or tag as arguments. Users can run the command to set a desired layout per tag or workspace in their up scripts to make it theme-able. Keeps it from propagating another setting throughout the code. Is that overly simplistic?

AethanFoot

comment created time in a month

pull request commentleftwm/leftwm

Add theme checks to `leftwm-check`

I'm looking at the xdg crate and having a hard time understanding how to use the BaseDirectories::find_config_files method. It seems like the path to search should be self and if you knew a specific filename you'd use find_config_file. But if you could use the iterator that find_config_files returns, you could then match on the Item like this pseudocode

match file {
    "up" => check_permissions(file),
    "down" => check_permissions(file),
    "theme.toml" => check_toml_settings(file)
}
VuiMuich

comment created time in a month

pull request commentleftwm/leftwm

Layout Per Tag

In my head I equate workspaces to actual screen real estate and tags to collections of opened windows. This feature applied per workspace would allow specific workflows to take advantage of specific monitor dimensions/orientation. It would also allow for tags to define a certain workflow that could be set up on any workspace/monitor. With that in mind to maximize the utility of the feature I would consider having both options available but then there's the issue of which setting gets precedence and should that be user configurable? I appreciate as a newcomer to leftwm and development in general the desire to keep the code human readable. The layout manager idea makes a lot of sense in that regard.

AethanFoot

comment created time in a month

issue commentleftwm/leftwm

[Question] Is there any way to manage layout on per tag basis?

I like this idea. I would suggest users should be able to toggle "apply layout change to all tags" as a bool. If someone is expecting that behavior it would be very tedious for them to have to apply the layout to each tag individually.

tabetai

comment created time in a month