i3-gnome-flashback VS rofi-file-browser-extended

Or i3 with gnome for those who don't want to code up their own monitor hotplugging, ssh/gpg agents, media hotkeys, usb drive hotplugging, screenshots, theming, ...

Similarly, I just use i3-gnome-flashback and get a full set of gnome desktop environment goodies without having to do anything much.

Yet another of the long list of small reasons I run i3 within gnome-flashback.

For me with whatever tiling WM, I am not interested in creating my own Desktop Environment, so I run it within gnome-flashback to get all the desktop niceties like hot-plugging monitors, hotkeys for media, screenshots etc., ssh/gpg agent, compose key, and many more. I am not interested in rolling my own solutions for each of these in turn, only realize what I haven't set up yet right when I need it. See exwm-gnome-flashback, or i3-gnome-flashback.

gnome-flashback is the gnome ecosystem Desktop Environment that can have any window manager swapped in. I think that is what Regolith uses since they maintain i3-gnome-flashback, that I use.

In both cases I used gnome-flashback to get a curated Desktop Environment without having to roll my own - e.g. i3-gnome-flashback and exwm-gnome-flashback.

In my case, i3-gnome-flashback. As a result I have the typical desktop setup where the Gnome settings panel can control the monitor layout, and it remembers previously seen monitors and restores the layout.

To avoid having to build your own desktop environment, you can use it within an existing DE that allows alternate window managers. I use i3-gnome-flashback.

i3-gnome-flashback provides a way to use many GNOME tools with i3 (such as the control center): https://github.com/deuill/i3-gnome-flashback

I'm a i3wm / sway user ... I've got several keystrokes, including a file browser done using rofi. Maybe something like this, tied to a keystroke https://github.com/marvinkreis/rofi-file-browser-extended

I am using Rofi and have been happy with it for like few years now. I use it to both run programs and, instead of alt-tab, to switch between top-level windows (applications). There is also a relatively recent add-on that extends it to open local files as well.

wget -O ~/rofi.deb https://launchpad.net/~cppiber/+archive/ubuntu/ppa/+files/rofi_1.6.1-1ppa1_amd64.deb sudo apt install ~/rofi.deb rm ~/rofi.deb sudo apt install libcairo2-dev cd ~ git clone https://github.com/marvinkreis/rofi-file-browser-extended cd ~/rofi-file-browser-extended/ cmake . make sudo make install cd ~ && rm -rf ~/rofi-file-browser-extended/

Hi there. I am trying to write my first ebuild to learn how it works. I've chosen this (https://github.com/marvinkreis/rofi-file-browser-extended) program. Nothing complicated:clone the repo - make - make install. So, I figured out that make in ebuilds is src_install() { emake DESTDIR="${D}" install} but I am stuck with this cmake thing. There are so many entries in the documentation about cmake, the more I read then more I get confused. So my question is obvious: what is the best way to deal with this cmake thing in this particular case?

or you can use this too https://github.com/marvinkreis/rofi-file-browser-extended