You may be diappointed to know that Windows' cmd.exe will automatically open the default associated program, so all you need to do is enter the filename if you've associated image files with a default viewer: http://superuser.com/questions/246825/open-file-from-the-com... (I suppose a similar thing could be done on *nix with a suitably modified execlp()/execvp().)
Freedesktop systems get you an 'xdg-open' command (there's also 'gnome-open' for GNOME, and 'open' for Mac OS X). On Linux you should be able to wire up binfmt_misc, the plugin system for execve, to xdg-open.
cat tmp.png "Yep that looks like it's right" git add tmp.png
Whoopee, you saved one keystroke (`eom tmp.png` "Yep, looks good. Presses Escape ") and if you become interested in any data from previous commands' output you'll have to scroll up more / live with a larger window than otherwise because now you've got an image sucking up n rows in your terminal.
Look at IPython and DrRacket to see why inline images can be useful in REPLs. With DrRacket you can not only view, but also create and combine images one step at the time, always seeing the latest form of it. And then you naturally end up with a script for doing the transformations needed to get your desired result.
In short: the time savings introduced by shortening the feedback loop tend to add up. There is a reason why Web developers now use auto-reloading solutions, despite the fact that it saves "just one keystroke" (F5 in this case).
Hello. I'm the author of Black Screen, and I'm upset this post has appeared on Hacker News. The terminal is at a very early stage; I don't even use it by myself. Although, it's nice to see that people show some interest.
Can you use another npm namespace? . npm install black-screen is far better t'han "install-all" for many reasons: better npm search, no namespace pollution, more semantic than such a generic name. Please consider to change it.
it hasn't been published to npm yet. the instructions are for cloning the repo and installing it locally to test. that's an install script
I would really love it if one of these web-based terminals managed to stick around. Just being able to view images in a terminal would be amazing. The trouble with building on web technologies seems to be that the overhead is just too high (eg. Atom) considering how many terminals the average developer has open at a time. I guess at least since it's based on Electron, it might have more longevity than something built…
Just being able to view images in a terminal would be amazing What are the advantages of that over using a dedicated image viewer program?
Wayland and its associated protocol stack is old, crufty, and written for a use case that doesn't exist anymore. We're planning to get all the major toolkits migrated to DisplayWebKit sometime within the next two years.
That's a confusing assertion. Wayland is only a few years old, and has only very recently seen anything approaching widespread usage. What do you mean by "Wayland is old"? And, who's "we" when you say "We're planning to get all the major toolkits migrated to DisplayWebKit"? I'm not trying to be argumentative, I just don't get where you're coming from.
It's supposed to be in the spirit of "what we'll hear a few years from now about Wayland" just like we're hearing it now about X11.
cat tmp.png "Yep that looks like it's right" git add tmp.png
You may be diappointed to know that Windows' cmd.exe will automatically open the default associated program, so all you need to do is enter the filename if you've associated image files with a default viewer: http://superuser.com/questions/246825/open-file-from-the-com... (I suppose a similar thing could be done on *nix with a suitably modified execlp()/execvp().)
I would really love it if one of these web-based terminals managed to stick around. Just being able to view images in a terminal would be amazing. The trouble with building on web technologies seems to be that the overhead is just too high (eg. Atom) considering how many terminals the average developer has open at a time. I guess at least since it's based on Electron, it might have more longevity than something built…
Just being able to view images in a terminal would be amazing What are the advantages of that over using a dedicated image viewer program?
Hey thanks for replying & I hope my comments didn't seem snooty. I've thought a lot about how to solve this problem and was disappointed by the way some past attempts have just ignored the infrastructure that ensconses current terminals. And its a real shame that so many tools just hard-emit ANSI escape codes - there are even some TUI frameworks that do it. The problem I see is that you seem to have the terminal doin…
Hey. Not snooty at all. I understand your pain: once I tried to open Vim in this Kickstarter terminal project - Xiki - and was disappointed in the same way. Perhaps unexpectedly, Black Screen is both a terminal emulator and a shell. I tried hard to avoid going with writing a shell, but the existing ones simply don't fit. It's even hard to know when a child execution has finished. And I want smart autocompletion, so I…
I think for this to work you just have to create a shell and a terminal, to have a killer app that your terminal is the paltform for (realizing this is what kept me from ever moving on the idea). But my point is that I think the shell component absolutely must communicate with the terminal component over the tty subsystem using an extension of ANSI Escape Codes, defined in a terminfo page, so that the terminal component is only concerned with how the information is displayed, and not what the information is.