dotfiles VS vis

I bit the bullet and moved my mappings around. This is wholey unrelated, but do you know if stumpwm allows you to set the split size in dynamic groups? Like in dwm you can set the master window to be 50% of the screen with clients being the other 50%. So far in stumpwm I cannot find how and it seems hardcoded to 55%.

I am trying to get stumpwm feeling a little bit more like an integrated environment visually. Currently I am attempting to fix two problems that would create that integrated feeling. The first one is adding smart border functionality. Basically smart borders are is when only one window is open no border is shown, but if more than one window is open a border is drawn. I tried researching this, but I can not find anything. I am also wanting to try disabling borders all together. I have never done this before so I have no idea if I would like it. I made the proper changes to my configuration to remove any border and ignore size hints, but I still have that stupid padding around terminals. Does anyone know how to disable those?

I have been doing research trying to figure out what software in my current toolchain has a Lisp, specifically Common Lisp, alternative. Having looked around I have been able to find a few thing.

I am trying to setup my workspaces for stumpwm, but am running into a wall due to not being able to find much documentation, is there is even support, for a few things I want to do. For some background, I am coming from dwm which I have used for a few years and even forked a few times. In dwm I had a rather simple, but extremely useful, setup where I would store specific types of programs on specific tags. I was able to figure out getting this done in stumpwm and it working just fine. The main issue with this portion of my workspace setup is that the Default workspace still exists. I have tried to figure out how to delete it, but cannot. I know how to rename it, so I could just do that and use it for my terminals, but the issue arises where I have no idea how to change it from the default stacking layout to the dynamic one. Any advice? Additionally, is there a way to get something like dwm's fakefullscreen?

My brain hurts, I did this and now it just works.

I am working on rebuilding my software toolchain around Common Lisp, because it is amazing. I have already started moving to sbcl from zsh, thanks to help from this subreddit and a friend, as well as moving away from my dwm fork to stumpwm. I am looking at what programs I have left to find replacements for and I know I am moving to either lem or gnu emacs, hopefully lem, from nvim and nyxt from firefox, but there are three programs I cannot find CL replacements for, my terminal, screen locker, and dynamic menu. The last two will be a pain, I know, but with the terminal I was shocked to see little to nothing online. I was able to find CLIM implementations of terminal emulators, but the one I found which I lost the link to is built into a desktop environment; I also don't know if it would run under X11 or Wayland. I was curious if there was someone here who would know of a terminal emulator that was written in CL? It doesn't need to be fancy, in fact the less fancy the better. I am just trying to figure out if I refork st or if there is a CL terminal I can use.

I am unsure if you have interest, but is the final working product :D Thank you again! https://gitlab.com/FOSSilized_Daemon/dotfiles/-/blob/main/src/dotfiles/home/.library/generic/common-lisp/stumpwm/common-lisp/key-binding.lisp

I am unsure if this would have any impact, but I am making some changes (as well as this) to sbcl; none that should cause this though.

An update to my other comment. I can confirm that the issues I am having are due to cl-repl. I took my exact configuration, commented out the first line of my replrc.lisp, hardcoded a require for asdf, using find-package always returns nil for some reason with asdf I don't know why, and then symlinked the file to ~/.sbclrc and everything loaded fine and ran fine. I am unsure what is up with cl-repl. I think I would rather use sbcl anyway, but I just need to figure out tab-completion, sytan highlighting if possible, and then determine how to check if asdf is installed to load it (I know I can always require it, but I want to proof this configuration in case I use it on a repl that does not autoload asdf).

Porting my shell configuration to cl-repl in order to help me learn common lisp. So I have my asdf system being loaded in my .replrc and I know things are being loaded there just not this code for some reason. If it helps the code is here.

Another editor that people might be interested in (and I think more people should know about) is https://github.com/martanne/vis. It is, in some ways, the opposite of Ki; instead of straying further from vim, Vis is just Vim + good multiple cursor support + sam-styled structural regexes (I didn't know what those are before using Vis, I consider it a detail of how the multiple cursor interface works).

Thus, Vis is easier to learn than Helix/Kakoune and gives you (IMO) the most useful feature of Helix/Kakoune.

Unfortunately, Vis is also a bit bare-bones, I don't think it has LSP support for instance.

> I wonder if the author has ever heard of vis[0]

Yes.

https://github.com/martanne/vis/wiki/Differences-from-Kakoun...

https://github.com/mawww/kakoune/wiki#onboarding

> which imho fulfills far better each one of those premises

Not very motivated for such a harsh critic..

If you want an editor that uses Sam's structural regexes with keyboard-focussed vi-style interaction, you might be interested in https://github.com/martanne/vis

Not Rust, but there's vis which aims to be a Vi(m) inspired editor with Sam's structural regular expressions.

I do not use vim nor a WM nor a Thinkpad, but I do use vis. It's great.

> They either break from Vim's model (kakoune, helix) or follow Vim along with all it's flaws (Neovim, Vis).

I am sincerely curious of what flaws from Vim has Vis inherited, in your opinion.

I have the impression that the design idea of Vis is taking only the modal design of Vi (not Vim), plus the structural regular expressions of Sam, then make it as clean as possible with programmability via Lua plugins.

In fact, the state non-goals [1] seems to clearly distant itself from Vim.

[1]: https://github.com/martanne/vis#non-goals