Earlier quoted context omitted.
While, I understand your dislike of Vim, Vi, Nano, Emacs, etc. (I can't work in them for extend periods of time either do to hand problems) They remain essential tools for many programmers and system administrators. Sometimes, you don't want to have the file pulled down and edited in a local edit and pushed back even if it is seamless. The benefits of inplace editing on remote machines is invaluable. I think this is…
There is potential for TermKit to send files to your client's Vim, which opens a lot of possibilities. For example, it would be easy to have files from two different servers open. It would also reduce the number of places you need your configuration files. TermKit's author may dislike Vim, but I suspect that he's helped its users in the long run.
TermKit - a graphical terminal replacement
191–200 of 208 posts
Re: TermKit - a graphical terminal replacement
#192cat a.png -- show the image in a tiny terminal, but I have a billion pixel screen.
why not just open it on the image viewer window?
you advocate this even for editing plain text in vim!
think that if you had learned to use X your days would be more productive... maybe not as cool...
Re: TermKit - a graphical terminal replacement
#193Earlier quoted context omitted.
Pretty sure Emacs has menus: http://jrock.us/emacs-menus.png
It does. The problem is, the terminology in the menus is completely inscrutable (i.e. many commands are named unintuitively), the menus are poorly organized, they have a small subset of all the commands, etc. I've never been able to learn any of the shortcuts from the menus.
Enjoy programming in Notepad.
Re: TermKit - a graphical terminal replacement
#194Earlier quoted context omitted.
It is amusing how we hackers, who are supposed to embrace change, become as Luddite as anyone else when our sacred tools are questioned. Personally I see room for this and a whole lot more. I'd like to see an amalgam of this and the traditional terminal (easy way to pull up a traditional terminal if you need it). There is no need to "replace"; I think this makes a fine addition to a hackers workspace.
Bloomberg found the same thing when they tried to redesign their terminals for traders - existing users were so invested in their knowledge of the "incantations" of the old interface that they were hugely resistant to a UI with a more modern learning curve and interaction. It's very hard to make a product that essentially devalues things that your customers spent a lot of time learning. You're probably better off ign…
I'm quite bad for upgrading for upgrading's sake but I can understand why, of all people, traders at Bloomberg didn't want any kind of learning curve on their terminals.
Yes, it's clearly better but users don't always want to change to something that does what they already do in a more modern way.
Re: TermKit - a graphical terminal replacement
#195Earlier quoted context omitted.
Bloomberg found the same thing when they tried to redesign their terminals for traders - existing users were so invested in their knowledge of the "incantations" of the old interface that they were hugely resistant to a UI with a more modern learning curve and interaction. It's very hard to make a product that essentially devalues things that your customers spent a lot of time learning. You're probably better off ign…
The thing about changes involving a "more modern learning curve and interaction" is that it's replacing something that already worked and users knew how to use. I'm quite bad for upgrading for upgrading's sake but I can understand why, of all people, traders at Bloomberg didn't want any kind of learning curve on their terminals. Yes, it's clearly better but users don't always want to change to something that does wha…
Re: TermKit - a graphical terminal replacement
#196Earlier quoted context omitted.
"if I did, I'd probably use Finder instead." The thing that strikes me as very, very cool about this project is that you might not need the Finder at all any more.
See, here's the thing: I like Finder. It's not perfect, but sometimes it is very handy. Even if TermKit ends up implementing the complete functionality of Finder, I'm not sure why I'd particularly like to have that functionality in my terminal window. And if it's only implementing the one Finder view I virtually never use? Forget about it. You know what would rock my world? A "lsf" command that emulated "ls" as much…
Re: TermKit - a graphical terminal replacement
#197Re: TermKit - a graphical terminal replacement
#198I virtually live in a full-screen emacs (on CLI or GUI). Emacs provides a somewhat nicer shell world than straight up Terminal.app. Emacs has copy & paste, a fully editable window display and its own command history.
Why do I bring this up? Because I feel that your application as currently demoed is not going to help me. I don't want to see GUI icons in general.
What I do like is your connection to the OS display layer. The ability to render out a PDF-inshell is pretty nice. Without having to go grub around for the right configuration, I can't just go "load foo.pdf" and have it pop up automatically.
So I really look forward to see what kind of cool explorations you do.