Reputation
234
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 18
Newest
 Quorum
Impact
~6k people reached

May
20
accepted Virtual Win 7 machine irreparable on reboot (with pending Windows updates)
May
8
revised Rsync takes very long time to return after completing file transfer
added 1 character in body
Apr
17
awarded  Quorum
Apr
14
asked Filtering `catch` tests by label when running with `ctest`
Apr
10
comment If 32-bit machines can only handle numbers up to 2^32, why can I write 1000000000000 (trillion) without my machine crashing?
@KorayTugay That, or anyone else who realized it also realized that it's not particularly important to the question.
Apr
10
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
I'm not sure how it got into that state, but I'll bet I could figure out how to coerce it if I understood better where xrandr is actually getting its info from.
Apr
10
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
.....Also, I just noticed that in my current (valid) setup, the native resolutions are not replicated between the modes listed for each screen: i.e., each screen has some set of common low-res modes (up to 1024x768) plus one high-res mode corresponding to the actual correct native res.
Apr
10
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
@Chris The names aren't a big deal, actually--I can just switch them if necessary, and in general they don't seem to change that much. The problem is that VBox apparently always reports the same set of "valid" modes for each monitor, but it's inconsistent about whether or not it reports the real hardware native resolutions. Actually....come to think of it, maybe it reports the valid set of hardware resolutions correctly, but xrandr is reading the resolutions at inopportune moments when one or more screens are disconnected. Where does xrandr actually get its "valid modes" list?
Apr
9
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
@Chris Well, it is a long question :) I haven't tried it--that would certainly be worth a shot. One strategy would be to set the "preferred" modes in gdm init, then use --auto in the i3 init (which seems to work pretty reliably when the preferred modes happen to be correct). Any idea if it's possible to manually set the "preferred" modes?
Apr
9
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
I use gdm3 and have i3 selected as the default desktop environment for my account.
Apr
8
comment Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
@JourneymanGeek The 4K has support for most of the standard modes at 60 hz, and support for larger modes (including 4K) at 30 hz. The SyncMaster appears to support most of the normal modes, with a native (vertical) resolution of 1920x1280. The i3 config script does support running a script at login; I'm using this feature to automatically run the script described above, which looks similar to yours, but I keep getting weird xrandr errors.
Apr
4
comment Rsync takes very long time to return after completing file transfer
@Hastur I've edited the question to add some output from -vvv. I tried putting 3 in drop_caches; the first time I tried this, rsync completed in about 15 seconds, but on subsequent trials it seemed to take longer. I'm going to try doing time rsync ..... to an empty destination directory 6 times in a row to get some more solid data. What do you mean about doing an rsync before I start the "real" rsync?
Apr
4
revised Rsync takes very long time to return after completing file transfer
added 567 characters in body
Apr
3
revised Cannot reliably automate xrandr settings in Debian 7 on VirtualBox
added 115 characters in body
Apr
3
comment Rsync takes very long time to return after completing file transfer
Er...the directory paths I'm giving are absolute paths. This should be obvious from the fact that rsync only ever lists and transfers the files I'm expecting, and from the fact that I don't get permissions errors.
Apr
2
asked Rsync takes very long time to return after completing file transfer
Mar
17
comment Vim: How to delete a vim buffer when you quit a file in vim
@sargas ...as long as the edit isn't incorrect....
Mar
6
accepted Suppress commit-message template with `git merge --squash` or `--no-commit`
Mar
6
comment Suppress commit-message template with `git merge --squash` or `--no-commit`
Yep, SQUASH_MSG is exactly what I wanted. I ended up just writing over it with my preferred template instead of deleting it.
Mar
6
comment Suppress commit-message template with `git merge --squash` or `--no-commit`
Note that your quotes surrounding variables should be escaped...