Live data from Hacker News

TermKit - a graphical terminal replacement

acko.net

171–180 of 208 posts

Re: TermKit - a graphical terminal replacement

#171

Excellent shortcut for previewing files from the terminal: #!/bin/bash qlmanage -p "$@" >& /dev/null Opens any file in Quicklook, ctrl-c to close, or use the mouse. If you want it to stay open, just add final &.

Added to my todo list. Thanks, didn't know about this one.

Re: TermKit - a graphical terminal replacement

#172
post #41

Earlier quoted context omitted.

Regarding your quote problem: the idea is that the highlighted token signifies "quoted string". I plan to add regexp tokens, user@host tokens, etc. each with appropriate autocomplete. I thought the current minimalistic approach was ok, but it might be worth to add subtle quotes around the edges to reinforce the idea. That's why it's made out of HTML/CSS...

"quoted string" or 'quoted string'? Big difference. :)

The difference is in whether escaping is necessary. What happens when you no longer need to escape things? It no longer matters which quotes you use.

Re: TermKit - a graphical terminal replacement

#173
post #36

Earlier quoted context omitted.

I'm having a blast and interpreting all the flak as a sign I must be doing something right...

I'm so impressed with that. If I was getting that much criticism (for something so obviously excellent!) I'd be shaking in my boots. :-(

Well, a few years ago I made this Line Rider video, and then 10,000 people on YouTube told me to get a life.

Who cares what people on the internet say, they're the ones wasting their time posting it.

Re: TermKit - a graphical terminal replacement

#174
post #25

Earlier quoted context omitted.

And on another note... it's been hilarious how people have been questioning my professional credentials just because I want to make something more usable. I've implemented over a dozen RFCs, can match regexps with the best of them and do know which end of a pipe does what ;).

I love the idea. But as someone who also loves vim, to hear that your vision of a new terminal excludes a tool as powerful and expressive as vim makes me sad, because it means that apparently I won't be able to benefit from this new terminal. I'll watch with interest, however.

If I can make TermKit deliver on its promise, then I'm pretty sure on of you vim guys will take a VT100 JS emulator and make it work in TermKit.

Again, the architecture supports it.

Re: TermKit - a graphical terminal replacement

#175

Earlier quoted context omitted.

Really? I see the same thing whenever you get a bunch of professionals together and start arguing about their tools. Doctors and different drugs/treatments, Contractors and brands of power tools. Programmers do seem to make the biggest deal about "all the fighting", everyone else seems to just accept that professionals are opinionated and arguing is how progress is made. But I'm on the inside with the programming stu…

Doctors and different drugs/treatments, Contractors and brands of power tools. From what I've seen, smart Doctors and Contractors eventually get to discussing empirical data and costs. Far too often, I've seen programmers just make up crap and state it emphatically.

Thanks for bringing up this great point.

I actually built in anonymous usage logging into TermKit using Google Analytics over SSL. It logs the types of commands you execute (no data). It's my plan to release this data back to the community regularly. I don't think anyone has done a large-scale survey of command-line unix usage before. Should be interesting.

Edit: and you can easily turn it off if you wish.

Re: TermKit - a graphical terminal replacement

#176
post #53

It's a pity that this is so difficult to try. The blog post has so much detail and effort put into it, but all that shine and polish disappears when you try to install it. Specifically Step 1 of the instructions[1] has a link titled "install node and npm" [2] which has the line 'git clone git://github.com/ry/node.git', which is incorrect. The correct URL (as far as I can tell) would be 'git://github.com/joyent/node.g…

I don't mind, the project is in too rough a shape to interest anyone but hackers. Please come back in a month.

Re: TermKit - a graphical terminal replacement

#177
post #121

Earlier quoted context omitted.

> especially in something like Vim. give me some help to learn the shortcuts as i work, FFS. on a GUI you look at the keyboard shortcuts beside the menu items, and get to know them naturally. This. I hate both vi and emacs for not having a usable menu system that lets me browse through and learn the commands as I go. I also think bash-completion, while a huge step forward in usability, really should have focused on i…

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.

Re: TermKit - a graphical terminal replacement

#178

Earlier quoted context omitted.

I wouldn't be surprised if Webkit was just as fast or even faster in rendering than your average Linux terminal emulator. About caring enough, yeah, that depends, maybe the world is ready for this now :) At least it isn't some overengineered XML grotesquery this time.

that webkit will render faster than a terminal emulator is just pure fantasy, is like saying that a smart phone with all the fancy apps will eventually use less power than a solar powered calculator. you ppl are addicted to osx overdesign. no graphical user interface will beat a keyboard in the right hands, like it or not. pure fantasy, hipster hackers

What was the last time you had any problems with the rendering speed of Webkit in reality? Have you tried the other link in HN, that boots Linux in your browser, with a terminal app, and it still manages to be fast even on my modest system?

Have you looked at some WebGL / Canvas based demos lately? There are now very efficient GPU offloaded rendering APIs that make rendering graphics a breeze, it is no longer a big-overhead thing. If you don't use fancy graphics you're underutilizing your GPU.

[also, TermKit is not just about fancy graphics, but also about user friendlyness/usefullness for some tasks that are not very well handled in terminals otherwise]

Re: TermKit - a graphical terminal replacement

#179
Looks really good (haven't tried it yet though). The concept is great. I'd like to see some TextMate/CommandT style functionality for file and path completion (I've been thinking cd'ing around in shells has been cumbersome ever since trying commandT).

Some other inspiration could be taken from zsh autocomplete.

Re: TermKit - a graphical terminal replacement

#180
Can't really say this or that about the project. It looks cool but I have no idea whether the user interface would lessen the friction between myself and the computer; it might just as well increase it.

But that's okay. We're not supposed to decide whether the prototype points to the right direction or not; we're just supposed to rant and ramble a bit about it.

However, the question of whether this turns out to be a good idea will be evident when and if TermKit delivers. In this context it means that TermKit or some of its derivatives turn out to be actually more useful than the standard Unix shell.

The indicator would be that instead of a traditional Unix shell, people start using TermKit in order to get more things done more easily and in shorter time.

Post reply on HN