terminal-survey

3 ms·

1.
by terminal-survey 9y ago
> I would love to use one of those fancy graphical terms that comes up on HN every now and then One of these (Black Screen) is among the many inspirations with which we started. > Any attempt to improve the terminal has to be somethin
2.
by terminal-survey 9y ago
As soon as the project is at a point where we feel comfortable showing it to a wider audience, we'll make a proper announcement and post it to HN (among other places).
3.
by terminal-survey 9y ago
You mean that it should scroll in the opposite direction?
4.
by terminal-survey 9y ago
I think the problem is that you only know if you care about the output after the fact. For example, if "make" runs through, I usually don't care about the output. But if "make" fails, then I want to read the error m
5.
by terminal-survey 9y ago
We are currently doing most of the work offline, so it's difficult to collaborate with a far-reaching network of contributors at this point. However, if you drop me a note at < 34c3-terminal-survey at posteo dot de >, I can put y
6.
by terminal-survey 9y ago
Yes, it would be nice if reflowing became more common. We are not sure if our spec requires the terminal to support reflowing (because of the resource usage implications), but the terminal must at least be able to announce whether it does r
7.
by terminal-survey 9y ago
> i've got ~20 bashes open in various tmux configurations. the amount of times i lost command history is infuriating (e.g. due to reboot or whatever). zsh does (has an option to) commit commands to the history file immediately when
8.
by terminal-survey 9y ago
Hi everyone, thanks a lot for the responses. Keep them coming! As mentioned in some of my replies, we have already considered some of the things that you mentioned (and incorporated them in our design), but your responses show that there is
9.
by terminal-survey 9y ago
Oh yes. We want to have an API where clients (i.e. programs running in the terminal) can receive actual key/pointer/touch events if they choose to. The terminal may retain control over a few crucial keysequences (similar to how Ct
10.
by terminal-survey 9y ago
We already have a solution for this sketched out on paper (not in writing or code yet, though). The idea is that the shell can split the terminal into "frames", where each frame acts as its own terminal. The shell would then use o
11.
by terminal-survey 9y ago
> At first I would state one curious fact: [...] That part is so nicely said I might just steal it for our manifesto. :)
12.
by terminal-survey 9y ago
> "cat" could never work of course We have an idea in that direction, where each program in a pipeline can optionally specify a file type, and the last file type hint in the pipeline determines how the stdout is rendered. So if
13.
by terminal-survey 9y ago
Our draft already contains a command for "set terminal into ignore-escape-sequences mode". I added that last week when someone showed how to hide malicious code in "git diff" by using specifically crafted control sequenc
14.
Ask HN: What do you love/hate about terminals? Would you change them?
109 points by terminal-survey 9y ago|200 comments