161–170 of 354 posts
One fateful day, VMWare and OS/X conspired to trash my shared filesystem, losing several days of uncommitted code in the process. Several days of uncommitted code? We need to have a heart to heart talk about your process.
How about if he is using Git? It is normal to work out of your local repository and only sync with the master occassionally, no? At least on projects that can tolerate such methods.
This has to be the most ergonomically inefficient set-up ever! I also cannot fathom how to work with 21" at least). And a tiling window manager. And a decent mechanical keyboard... ok ok.. Interesting setup. I'd be interested in knowing how it works out in the long term.
Certainly not "in vogue" and I don't know if it's feasible today. Still an interesting thought.
Earlier quoted context omitted.
How about if he is using Git? It is normal to work out of your local repository and only sync with the master occassionally, no? At least on projects that can tolerate such methods.
I push to a personal remote at least twice a day. Not doing so is asking for trouble.
Earlier quoted context omitted.
I see your point, but still, battery life/silence/portability doesn't seem to be worth the flexibility of having full osx esp when compared to an Air
The restrictions of iOS make me happy: I have a simple consumer brick. I can wipe it and restore it on a different device without losing a single byte. It never stutters, never misses a frame. I never need to care which programs are running or the layout of the filesystem. The psychological effect of this is surprisingly powerful.
$800 gets you a pretty nice laptop. I don't see the advantage of this approach at all.
For anyone still using gnu screen, tmux.
Looked at it; didn't see any compelling reasons to switch; went back to screen. Screen is for the most part "good enough" that any replacement that aims to supplant it completely needs to either be vastly and obviously superior or enough of a drop in replacement that it doesn't require any effort to switch (I'm most definitively not investing time updating config files or changing key presses unless the improvements…
I REALLY like that the hardstatus line equivalent shows the command that's currently executing (think: bash, make, ./configure etc). That said, if you don't use the hardstatus line, I don't think there's much of a reason to switch unless you want multiple different size panes which screen doesn't really support.
Earlier quoted context omitted.
The only feature I care about is persistence. Is there a difference between Screen and tmux regarding persistence?
If you only need persistence, look into dtach. That's all it does. Both screen and tmux offer multiple persistent sessions, the difference is the command syntax. Back when I was deciding on a terminal multiplexer I picked tmux over screen because session sharing seemed to be done in a more sane way. But then again, had I used screen for any length of time I'm sure I'd have gotten used to it.
Can you really write code efficiently on such a small (9.7") screen?
I've written many tens of thousands of lines of C on my netbook, which has a 10.1" screen, also using Vim, so I believe it's possible. Still, I'd really like just a smidge more space, especially in the vertical. At least 168 pixels, to be specific. That's one advantage he has with the iPad - he can easily switch between portrait and landscape, depending upon his needs. I'd love to be able to occasionally turn my netb…
By the way, Moconnor, have you given Panic's Prompt a try?
Earlier quoted context omitted.
Looked at it; didn't see any compelling reasons to switch; went back to screen. Screen is for the most part "good enough" that any replacement that aims to supplant it completely needs to either be vastly and obviously superior or enough of a drop in replacement that it doesn't require any effort to switch (I'm most definitively not investing time updating config files or changing key presses unless the improvements…
shrug Maybe. It's all about what's valuable to you. I switched to tmux because it is better maintained and it has better screen splitting functionality. I also mapped screens commands over to tmux, so the switch was basically painless. Took all of 15 minutes. If you're cool with screen, you're cool with screen. No worries.
And I don't use the screen splitting at all - I use splitting a lot in emacs, but never in the terminal, so that's basically a non-feature for me.
I want to create, remove and switch between windows, and have a status bar showing their names. That is all.
I guess these are the reasons I've never seen the point in switching.