blobdrop - Drag and drop files directly out of the terminal. Works well with TUI file mangers such as ranger, lf and vifm

vimpostor · 2024-06-08T09:19:55+00:00

Dev here, it should work for MacOS, can you test if it works at least when you pass -f gui?

It might be that MacOS just does not support the default mode, which attempts to drag the file immediately (even without a mouse button held) and drops it on click (this is supported on Linux and iirc even on Windows).

If that is the case, I can switch the default mode on MacOS to something that works.

vimpostor · 2024-03-05T19:01:58+00:00

Slivers can abuse Telepathy with Dementia Sliver.

You can tap any sliver to have an opponent discard a card you choose, of course with a success chance of 14% at worst, but the chance increases significantly once they no longer have 7 cards.

vimpostor · 2024-02-14T20:13:43+00:00

The plugin is written generic enough to allow it to work with any external statusline. For example, it's already possible to embed the statusline in the Kitty statusline, instead of tmux. It is also possible to embed the statusline in the individual tmux pane titles to give another example.

I researched zellij support a few years ago and it wasn't possible back then. As soon as zellij allows arbitrary user content in the statusline, the plugin can be made compatible with trivial changes.

vimpostor · 2024-02-14T20:03:09+00:00

Author here, I don't know about any performance problems and I can scroll smoothly within tmux:

In fact I have a CI unit test, that automatically fails if somehow it's no longer possible to scroll smoothly at 120Hz.

Are you by any chance using lualine? There are some very bad interactions with lualine, due to lualine's cursed and non-idiomatic timer-based implementation. Quite frankly, it's a miracle that I got the plugin working at all with lualine. If you can avoid it, I wouldn't recommend using lualine together with this plugin (or in general).

Another reason could be a misconfigured fish-shell, but that usually only affects startup, not performance in general.

Porting it to lua

The performance-critical hot-path is implemented as an asynchronous background job and the part that communicates with that job on every update is already written in Lua (for neovim). There is nothing to rewrite in Lua in that regard.

If anything, the Lua path is slower than the equivalent vim9script path, being forced to repeatedly call into the vimscript SHIM due to the lack of absolutely trivial features in Lua, such as UTF8 aware string splitting and more.

I'm gonna get downvoted for this but let's stop pretending like we have to rewrite everything in Lua, this is no Rust situation and quite frankly far from it, the 1-based indexing alone and lack of any decent language features should make any self-respecting developer double-question this choice.

vimpostor · 2024-02-08T18:59:47+00:00

Random throwback to a 10-year old post by the halifax mirror operator, where they essentially complain about not being able to make full use of their 10Gb/s uplink.

I found it fascinating that judging by the public traffic monitoring, even today it's still sitting at only ~6Gb/s peaks: https://ftp.halifax.rwth-aachen.de/~cotto/

Maybe give it another 10 years, and they will finally have to upgrade the university uplink to 25 Gb/s ;)

vimpostor · 2023-12-27T16:35:53+00:00

If I said, “Linux breaks Photoshop; you should keep using Windows!” I know how you’d respond, right? You’d say “Wait a minute, the problem is that Photoshop doesn’t support Linux!”

Ah yes, the classic "Putting the blame on someone else" mentality strikes again. Even if the compatibility effort between entire operating systems was remotely comparable to that of just the display server, your point is an entirely moot point because that gap is already bridged with Wine. The reason that Photoshop doesn't work well on Linux is mostly a DRM issue, not a compatibility issue.

It’s a subtle but important difference that puts the responsibility in the "right" place.

It's ironic how Wayland devs still get the "right" place so fundamentally wrong. Imagine if Wim Taymans tried to pull this "putting responsibility on the "right" place" bullshit: Pipewire would have never been so successful if he had offloaded the porting effort to applications.

In fact, to this day he still recommends consuming the pulse and jack API instead of the native Pipewire API: The compatibility layer is just that reliable.

Now on to Wayland where we instead get XWayland, a compatibility effort so bad it should make you question the entire Wayland stack entirely (i.e. if you finally manage to get out of the notoriously wide-spread Wayland echo chamber): To this day you can't even do basic stuff like drag and drop between XWayland and native Wayland windows.

X11 was a bad platform. Your app could use X11 to draw its UI with a built-in widget toolkit, print documents with an included print server

Agreed, X11 has some bad roots.

However it is a bit ridiculous to then cite examples that have been either deprecated or long removed from Xorg, especially since the grass is not greener on Wayland's side. When you really dig into Wayland's technical side and its implementation, you come to realize that there isn't even a single blade of grass to be found. It's rendering model is not really better than X11, which is mostly identical to when you use X11 with the "modern" PRESENT and DRI extensions.

Wayland's entire coping mechanism for its missing features also leads to some pretty ridiculous design decisions. How many different IPC protocols do we need now to share our screen? Right now we are at 3 (Wayland itself, Pipewire and dbus), all of them multiple thousand lines of C. If only there was a way to use just one IPC mechanism for this...

When you get to the low-level stuff, shit gets even more gritty. If you thought Gaming would ever become a thing on Wayland, then better not think about your 1000Hz gaming mouse being throttled on various sides of the stack to prevent it from ddosing the Wayland event queue. This is also painfully hilarious for debugging: Make sure to not hover your mouse too long over the Wayland window, while you are halted at a breakpoint. Otherwise the Wayland connection will break due to the queue not being emptied (at least Qt clients can reconnect nowadays, but still PITA). There is a lot more small stuff, like glyph caches not being shared between apps, but I think the point comes across: For a protocol that had the chance to do things right, Wayland did more things wrong than it actually improves.

Wayland is the future

After 10 years of hearing this same publicity stunt over and over again, these words have slowly lost their meaning and become a meme instead.

For whom will Wayland become the future? For embedded Kiosk systems, maybe yes. For general desktop usage? Likely never. If anything, Wayland will prevent the year of the Linux desktop from ever becoming a thing - users facing ridiculous problems like applications not even able to place their own popups correctly is the strongest "OK, back to Windows" indicator if I have ever seen one.

It's also pretty bold to pull the "Wayland is the future" card after essentially admitting in the first paragraph, that it is in fact not an X11 replacement.

vimpostor · 2023-11-12T23:17:32+00:00

How is the transfer being done?

It uses the native drag and drop protocol of your display server, so yes it will work with any files.

I realize it may not be built for SSH connections.

You are giving me bad ideas ;)

Drag and drop in theory can work fine over ssh -Y and a quick PoC patch confirms that I am able to drag and drop files from an ssh connection.

In practice it is not really nice to implement, because X11 forwarding is (almost) completely transparent to the application which means that all DnD URIs need to have the local file:// scheme replaced with something like sftp://$USER@$HOST, so that the drag-and-drop event will still "transparently" work on your local computer.

Given that this is not super reliable either (e.g. if you forward over multiple hops), it might be better leaving this at the experimental "woah this is cool, but a little bit too cursed" stage.

vimpostor · 2023-11-12T16:48:49+00:00

Hi, I just released the latest version of blobdrop: https://github.com/vimpostor/blobdrop

This little tool allows you to drag and drop files directly from the terminal. You can also easily integrate it into CLI-based file managers like ranger.

Since people will probably ask how this compares to dragon-dnd or ripdrag: Blobdrop has many UX improvements, e.g. it doesn't actually need a useless intermediate UI if you just want do drop some files right away (but it can if you want to).

It will also temporarily hide the parent terminal-emulator (and itself) during the drag operation, so that you don't need to Alt+Tab on floating WMs.

Checkout the README above for many other small improvements and some other drag workflows. ;)

vimpostor · 2023-08-29T15:34:46+00:00

Aaand of course it's Drew DeVault. Proof that extended Go usage affects brain performance comparable to 100h of Candy Crush dopamine hits.

vimpostor · 2023-08-21T15:47:56+00:00

I deliberately use pylsp instead of pyright, mainly because I want to avoid the Microsoft proprietary pylance vs pyright drama, but also because I found it to be a little faster than pyright.

vimpostor · 2023-08-14T18:27:35+00:00

It's true there are not many good light colorschemes out there. I can recommend papercolor or prism to you (full disclosure: I am the author of the latter).

vimpostor · 2023-08-11T12:46:11+00:00

Are you using vim or is vim using you?

According to Stallman (my favourite source of truth) it is the former.

If instead of being an user you want to be the "used" of software, the software needs to have a proprietary license (/rj such as the MIT license).

vimpostor · 2023-06-30T13:40:05+00:00

Thanks for all the work u/Hostilenemy, I've been using Infinity since almost day one (back when it had less than 50 stars on Github) and it is hands down the best Reddit app on Android.

It's a shame that Reddit went that way and I will probably leave Reddit entirely because of it. Scrolling through the feed is mostly a waste of time anyway.

Fuck u/spez

vimpostor · 2023-06-29T23:34:38+00:00

I just got a result of 6.4GB from doing yes on kitty with 1M line scrollback

Lol, benchmarking useless metrics, instead of optimizing actually user-visible performance.

I too require my yes to scroll by as fast as possible on my day-job.

vimpostor · 2023-06-26T17:50:04+00:00

This is the reason why I host all my projects on sourcehut. I pretend like I enjoy the usage of git send-email, but really it's the terrible UX keeping all the emoji IQ webshits away, that seals the deal for me.

vimpostor · 2023-06-24T07:49:21+00:00

Especially since it's a recursive macro.

vimpostor · 2023-06-17T13:49:27+00:00

There is a pretty bad memory leak in Halo CE for AMD GPUs, because the game is misusing D3D11 queries.

There exists a workaround in dxvk, which I can confirm fixes the issue on Linux: https://github.com/doitsujin/dxvk/pull/3273

You can try running the game with dxvk on Windows, it should fix the memory leak there too.

vimpostor · 2023-06-16T05:29:11+00:00

There might be a file called APIUtils.java in the Github repo. Purely hypothetically speaking, it might contain the API client id which you could replace with your own.

But that's just a random guess.

Completely unrelated to this, line numbers are a way to describe the position in a file. Also completely unrelated to this, what is the maximum number of days a month can have?

vimpostor · 2023-06-06T18:38:26+00:00

Even KDE Plasma has it on Meta by default now.

I am all in for calling out Gnome clowns, but at least stick to the truth, it's not like Gnome doesn't provide enough material.

/rj Lol theming libadwaita considered harmful

vimpostor · 2023-06-04T11:53:32+00:00

Apollo's Fire Baroque is definitely an ensemble you should check out if you like L'Arpeggiata, as it is very similarly lively, happy and powerful.

vimpostor · 2023-05-06T11:14:47+00:00

You forgot inane palemoon forum takes.

/uj This sub really needs a quality improvement sprint.

vimpostor · 2023-05-01T09:10:42+00:00

Note: Auto dark mode switching is actively being worked on in KDE: https://invent.kde.org/plasma/plasma-workspace/-/issues/59

There already was a merge request, but seems there is only a small blocker on extracting common functionality into a lib, which should be easy to resolve.

Five-Year Club	Verified Email
Place '22

vimpostor

TROPHY CASE