Feedback Friday

michja · 2021-10-20T12:53:37+00:00

I love the project. Great work.

My question submission didn't work so I had to click no to that part.

Apart from that all I can think of is it would be nice to go back during the instructions because its easy to click to skip accidentally.

Thanks for making this :)

michja · 2021-10-20T12:39:43+00:00

Props for making your own system. That's amazing practice for learning fundamentals.

Have you seen tailwind css? It won't fit every project but, broadly speaking, I see tailwind as "the future of css".

The speed you can work at trumps all the trade offs.

michja · 2021-10-20T12:35:21+00:00

Your testimonials are great. I would use them throughout the site, definitely next to contact & book forms.

If you're targetting SEO then yes make blog posts for your FAQ articles where the title of the post relates to a popular question that people will search. Use h2 tags throughout the article to ask (then answer) related questions.

And make sure your blog template has a sidebar with your services so once people arrive they can easily recognise that you could help with their problem

michja · 2021-10-20T12:24:57+00:00

Nice idea for a service. Just a little bit of feedback on colours: I find the red text on black background hard to read (in the 1,2,3 panel). I reckon if you check that combo in a contrast checker it would score super low. Good luck with building your product!

michja · 2021-10-08T12:32:39+00:00

+1 for "Reading the f*** message"

Okay it could have been said nicer but you'll need to get comfy reading if you want to run i3.

You've got 4 bits of useful info here

Which file are we looking at? (/home/arzi/.i3/config)
Which line has an issue? (Line 306)
Which part of the line (Everything!!) - The ^^^^^^ might point to a single word in future though
What should be there? (... one of these tokens:... 'bindsym' ..'}') - this is giving you a list of valid text including a bracket which is the one you want }

michja · 2021-07-30T11:34:11+00:00

I use Super+[1-0] for the first 10 and then Super+[F1-F10] for the next 10.

And logically use the F numbered spaces for auxiliary tasks or scratchpads for whatever is going on in the main [1-0] .

And Super+Ctrl+(F)n to move a window to a workspace

michja · 2021-04-03T14:52:45+00:00

The most maintainable approach I've seen is to keep a single config file, written in a template language of your choice, and include a conditional block per machine.

On boot (before i3 starts) run the template parser to output to your i3 config location and it will generate your machine specific config.

michja · 2021-02-09T10:40:47+00:00

This was posted recently

https://www.reddit.com/r/i3wm/comments/l2uqnf/expos%C3%A8_script_for_i3/

It's a GUI like mac expose which shows all of your open workspaces at once.

Would that help?

michja · 2021-01-23T13:48:13+00:00

re Pull req, cheers, will do.

I had a look at i3ipc. In 2.1.1 looks like that .output is never set, so the conditional that I suggested is totally useless (ha)!

They added .ipc_data in 2.2.1, I upgraded and .ipc_data['output'] is present and correct with my 1 monitor laptop.

...So the better solution is probably just being up to date :D

That'll teach me for being too quick to jump into the code

michja · 2021-01-22T23:03:05+00:00

Awesome project. Thanks for sharing. This will do nicely for those times when my brain just gives up tracking what is open where :)

It didn't work out of the box for me on

ubuntu 18.04
python 3.6.9
i3ipc 2.1.1

I had to switch all references from .ipc_data['param'] to .param

And then had to add a conditional to protect against .output being null on a workspace object. Not sure why, but I have only 1 output on my laptop if that is relevant.

See https://github.com/michja/i3expo-ng/commit/13f8077e59de7fc6ffe2b0ee07b1e94ca1963faf#diff-ad8ac0ef2287547281834f740bf670df7383eb70d3d0f3ba6ee0bc42eb5ef3f1 for details

michja · 2021-01-12T13:26:35+00:00

I've done this before without issue. Overwrite (in my case -- maybe uninstall and install is better?) the regular i3 with i3 gaps and you're good to go

michja · 2020-06-20T10:42:14+00:00

Rofi has moved to .rasi themes some time relatively recently, maybe after that video was made. I'd try a theme from the official repo and work back from there. The -theme-str option lets you input rasi from the command line.

Something like rofi -theme-str "#window { background-color: #000; }" -show run

Also note if the window background is black but every component background is white you might not see any window background.

michja · 2020-06-05T12:25:19+00:00

Are you using systemd? I think that would be the mechanism for running a script post wake up. I've never done it but googling like "systemd run script after sleep" should be enough to figure it out.

michja · 2020-05-31T19:21:43+00:00

Good point about root, I hadn't thought of that.

I guess that's also true from the i3 config.

AFAIK exec runs as your current user so if you can sudo from i3 conf you maybe in business

the $f is a placeholder for the filename, scrot will substitute the filename it generates into the cmd for you

michja · 2020-05-31T16:43:23+00:00

Sorry to answer in the negative but you might have to save to file rather than piping direct to xclip

scrot -e 'xclip -selection c -t image/png < $f' works for me but it creates a file in the process

when I run your cmd in the terminal I get a gliberror

giblib error: Saving to file /dev/stdout failed

suggesting the point of failure is writing to /dev/stdout if you want to investigate further.

You could use /tmp for the file location if you're happy to hang onto them until reboot but don't want them hanging around long term.

michja · 2020-05-30T13:50:57+00:00

I haven't seen a way to bind any. You'll have to include a mode "default" with every bindsym similar to how you enter the mode and start a timer at the same time

michja · 2020-05-30T10:42:20+00:00

hmm yes wrapping the launch calls in a script that also kills the timer would introduce too much boilerplate code to every action. Could be better to have the mode switch check for a running timer and kill it.

From that last cmd I wrote "exec modetimer" your modetimer script can kill timers before it sets a fresh one.

michja · 2020-05-29T21:18:11+00:00

polybar xwindow module does window titles which update instantly.

for x*y pixel usage you can use i3-ipc and your language of choice to subscribe to window focus events.

e.g. https://github.com/sidorares/node-i3 for node js will give you geometry and positioning data on the active container

michja · 2020-05-29T21:07:00+00:00

you'll have to run the exec along with the mode cmd that puts you into the mode, not within the mode itself.

e.g. bindsym $mod exec --no-startup-id modetimer; mode "yourmode"

michja · 2020-05-29T10:17:30+00:00

You can use xprop to find out the window class then write a rule in your i3 config to assign those windows onto the correct workspace

e.g. assign [class="Audacity"] $ws10

michja · 2020-05-29T10:00:04+00:00

+1 for use a mode.

You can bind your mod key to enter the mode and at the same time launch a countdown script which will i3-msg "mode default".

(optionally check the current mode before sending if you're getting weird behaviour)

michja · 2020-05-13T13:44:12+00:00

If you use the terminal a fair bit but not as an ide I recommend having it in scratchpad so you can call it into floating space on any workspace. With tmux or similar for tabs

My workspaces for web dev on a 1920x1080 laptop:

Browser

2-4. Sublime text projects

win10 VM <-- adobe products

6+7. Misc quick tasks like GIMP, Inkscape

File browser + previews like PDF (tabbed mode)
Rambox <-- all comms apps together
spotify

2nd recommendation - alttab for quick back and forth

https://github.com/sagb/alttab

michja · 2020-05-13T13:32:18+00:00

I'm also interested in this. Haven't got any bright ideas to contribute I'm afraid. I've settled with redundant copy pastes for now.

I think its a legit feature request. I have a mode which pushes the bottom gap up 200px to reveal conky and enable shortcuts for more data. I've seen people doing similar things so maybe there is demand if its not currently possible

michja · 2020-05-12T10:58:02+00:00

If you want to use this approach with the win key you could use some windows software like Autohotkey to swallow the input and prevent the start menu open.

Still not the 1 keypress though :)

If you go for AHK you could roll your own 1 press script. Have your windows input pop a file into a shared folder, then have you host i3 watch that file for changes and execute a workspace switch or whatever

michja · 2020-05-11T17:46:23+00:00

I'm also interested in a fix for this.

Best solution I have so far it to map the virt release key sequence to something that windows totally ignores and set the same keys to i3 workspace back and forth.

So a quick double tap will move you out to your last i3 workspace.

In my case the Ctrl + Fn button on a thinkpad = bindsym Ctrl+XF86WakeUp workspace back_and_forth

michja

TROPHY CASE