~exec64/imv#3: 
Read image from stdin, not just file paths

I still rely on feh for those use cases. Would it be possible ?

Status
RESOLVED INVALID
Submitter
~stacyharper
Assigned to
No-one
Submitted
2 years ago
Updated
1 year, 11 months ago
Labels
No labels applied.

~stacyharper 2 years ago

Okay it seems implemented. But I got a crazy issue that display a blank screen while I am in my HOME directory.

see: https://tube.missbanal.net/videos/watch/94e7200b-47b8-4fe6-a7bc-e87930620dcb

~exec64 2 years ago

That's really strange indeed. Can you capture the output of using strace when doing this in your home directory and in a subdirectory? I can't think of what would differ between those two cases.

~stacyharper 2 years ago

That's really strange indeed. Can you capture the output of using strace when doing this in your home directory and in a subdirectory? I can't think of what would differ between those two cases.

Mhh I cant reproduce anymore :S The command now works from my home again. Maybe just something was wrong with my system

~exec64 REPORTED INVALID 2 years ago

Ah, odd. Sounds more like some kind of race condition then. Perhaps if imv loads the image faster the curl provides it, imv handles waiting on stdin poorly?

Thanks for the update though. I'll close this for now since it's not reproducible.

~seerlite 2 years ago

This issue happens if there's a file called "-" in the current directory. imv opens that file instead of reading stdin.

I think imv should always read from stdin when passing - as the file argument, and only try to read the literal "-" file when passing an explicit path like ./-. This is how most tools that take - as a shorthand for stdin/stdout work.

~seerlite referenced this from #14 2 years ago

Carlos Eduardo referenced this from #37 2 years ago

~k0li 1 year, 11 months ago

@~exec64 can we document in the manpage that if you pass - as filepath it reads from stdin? That was not clear at all

Register here or Log in to comment, or comment via email.