467 reputation
2617
bio website trusktr.io
location
age
visits member for 3 years, 8 months
seen Jul 9 at 1:47

trusktr.io


Dec
13
comment Use touchpad while “typing”?
Thanks! This worked! I never accidentally touch the touchpad while typing anyways, so I need the touchpad to work for things like Gimp where you scroll the canvas around by holding spacebar and moving the mouse pointer at the same time.
Dec
13
comment Is Intel/Nvidia Optimus technology supposed to switch instantly between GPUs?
I think it might've happened when I upgraded to Win 8.1, shortly after turning it on for the first time (it also updated a bunch of Sony software).
Dec
13
comment Is Intel/Nvidia Optimus technology supposed to switch instantly between GPUs?
I definitely do know though, and it's quite annoying. Maybe it's a driver issue (but why would Sony let that happen?).
Nov
12
comment Is there a powerful yet lightweight vim-like keyboard-centric web browser out there (for Linux)?
Also try luakit: mason-larobina.github.io/luakit
Nov
11
comment testdisk - partition : write error
I also get this "write error". WHat in the world!! I just want to recover my lost partitions. :(
Nov
11
comment Recovered Files with TestDisk, but File Names and Folder Structure is Bad
@slm Seems like Tim Omaha joined just to answer this question. Too bas he hasn't replied. It'd be nice to get more info on PAR2 files. Never heard of it before.
Oct
27
comment Is there a risk of damaging a laptop with another power adapter make?
My laptop says 10.5V and I have an adapter that is 12V. Should I use it?
Oct
23
comment Mac OS X Terminal: How can I make my pico editor syntax highlight?
Don't re-learn vi, learn vim. It's so much better (you can have it behave just like vi if you want).
Oct
17
comment Smooth scrolling for vim in Mac Terminal/iTerm?
Another small (possibly negligible for some) advantage of using scrollable widgets would be that you could render a small mini-buffer similar to how Sublime does.
Oct
17
comment Smooth scrolling for vim in Mac Terminal/iTerm?
@romainl Yeah, syntax scripts seems like they could cause slow loads running on 5000 LOC. This'll be interesting to test.
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
Oh, I forgot to mention, and if you you haven't pieced it together already: these smooth animations I speak of would be pixel by pixel, not line by line. #:^)
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
(cont'd.) Lastly, but probably only the beginning, modern scrollable container widgets (like the ones in GTK3 or Qt) support inertial scrolling. Imagine being able to swipe vim with your finger and scroll it smoothly with inertia. Imagine pressing pageup or pagedown and the scrolling is animated with acceleration and deceleration.
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
(cont'd.) On the other hand, there may be plugins that rely on what's visible in the window (EasyMotion, for example, that updates the view to show you movement suggestions) and such plugins might have to do more calculations on the full length of the text when invoked. Another such example would be Signify, which would have to show git diffs in the gutter of the entire full length text (but that case probably wouldn't be too bad because Signify only uses two columns maximum, and only the rows that have changes).
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
(cont'd.) This has the potential to vastly improve vim's performance too. Think about this: every time you scroll the console vim or g/qvim windows (currently), vim has to rewrite almost every character on the screen. If the vim buffer was full length, and scrolling was handled independently by a smooth-scrolling widget, vim would only need to update one line's worth of characters at a time whenever you move the cursor to a new line (or better yet, a single character when you move forward or backward one character). This would be a HUGE performance advantage for vim!
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
(cont'd.) Window splitting could even be accomplished by duplicating vim's full-file-length output into a new widget and scrolling the widget smoothly to the appropriate position. This would all require some simple arithmetic and good knowledge of a nice widget toolkit. Window splitting (horizontal and vertical) and scrolling and resizing the widgets would be the. The rest would be a piece of cake to do (menus, tabs, things that gVim and qVim already do).
Oct
13
comment Smooth scrolling for vim in Mac Terminal/iTerm?
Hi @romainl. I wonder how vim behaves if the buffer size (windows size) is really big (i.e. the size of the whole file). GOtta test this out. Then we could put a vim buffer inside a smooth scrolling GTK (or QT) widget and scroll the entire vim buffer inside the widget smoothly. This would have the added benefit that the cursor could be easily hidden like with modern editors. When the user moves the cursor, the widget would know (using the same API gVim uses) and recenter the scroll position accordingly.
Oct
13
comment Mapping ctrl-backspace in terminator
(cont'd.) and thus adding some new escape sequence wouldn't really break much, if anything at all. It'd only add a way to distinguish ctrl+backspace for everyone!
Oct
13
comment Mapping ctrl-backspace in terminator
But unfortunately, in xterm, backspace (^H) is indistinguishable from ctrl+h (^H). Perhaps we can create a new escape sequence to be able to distinguish all three? I don't know how easy that is, but it seems like it'd be safe to do because with the current state of things (some terminals use ^? for backspace, others ^H, and vice versa) I can't imagine very many terminal apps (if any at all) consider the ctrl+backspace scenario (it'd be completely indeterministic due to the variety of terminals)...
Oct
13
comment Mapping ctrl-backspace in terminator
But can this be solved purely in the vim code base? How any code in the vim code base distinguish between backspace and ctrl+backspace if the terminal it is running in sends vim the same exact input for either key combination? Seems like this is something that must be fixed in the terminal that vim is running in, not vim. For example, Guake sends ^? for both backspace and ctrl+backspace, which makes them (AFAIK) indistinguishable. xterm, on the other hand, sends ^H for backspace and ^? for ctrl+backspace, making them distinguishable.
Oct
13
comment Mapping ctrl-backspace in terminator
@IngoKarkat See the above comment. ^