507 reputation
521
bio website
location
age
visits member for 2 years, 3 months
seen Dec 22 at 11:25

Shyy erny anzr - Naqernf Rvonpu


Dec
12
comment How to prevent `mv` from moving a collection of files into a single regular one?
@AndyzSmith Well, that's the very thing. You may call it a habit of mine to only ever use TAB for complicated directories or paths, but not for 2-letter-type ones.:) But come to think of it...perhaps I should really consider the latter case as well from now on.
Dec
10
revised screen & xterm: how to select text with the mouse in one only pane when window is divided vertically
added 260 characters in body
Dec
10
asked screen & xterm: how to select text with the mouse in one only pane when window is divided vertically
Dec
10
comment Why is my bash prompt getting bugged when I browse the history?
Ctrl-L only rarely helped me. But typing $ reset directly on the command line did the trick and brought my bash back to useable state.
Dec
10
revised “history” stops working when run inside bash script
added 4 characters in body
Dec
9
comment Saving bash history from multiple Konsole not working correctly
Sounds pretty much alike to the question coming up on bug-bash mailing list one year after this question was posted: lists.gnu.org/archive/html/bug-bash/2013-07/msg00092.html
Dec
9
answered “history” stops working when run inside bash script
Dec
9
comment Re-execute fc command from history
And I think that adding to history is dependent on the HISTCONTROL environment variable! In my case, it's set to ignoreboth, this means that both duplicate lines and those starting with a (white)space will be left out and never added to history. However, what if HISTCONTROL gets set to another value? I guess there will be a way to add the dupes too (if you keenly insist on it ;))
Dec
9
comment How to go to next screen in screen
ctrl-a +n works totally differently here! When I use screen together with xterm (my most frequent use), hitting ctrl-a +n will mirror my input from pane #1 into pane #2! Hence the only way out for me is the clumsy ctrl-a +tab.
Dec
9
comment screen & xterm: how to get window split vertically in custom ratio
"You end up creating a split with :split -v and resize it with :resize -h!" But that IS the very thing what I was on about! This necessity of having to use the complement of the option when creating/resizing. Eh...please? This feels (figuratively) as if you create an even square() but you need a circle_resize() method to resize the thing! ;) * laugh * New users must've been totally confused by that "dialectics" since the day when the option was implemented. My word on it. This should be made more logical and more user-friendly. (* plead over )
Dec
9
comment screen & xterm: how to get window split vertically in custom ratio
OK, I think I finally understood why it's called h. The h must be understood as horizontal AXIS (X, mathematically). Anyway, had I written screen, I'd have used resizeX and resizeY which would have been way more self-explanatory and would not (in complex split setups) force the user to draw the setup on paper to not mix up horizontal and vertical. Supposing you have 2 windows split 50:50, horizontally. Isn't it confusing that you need to change a vertical (-v) parameter to change the splitting ratio? To talk about X axis and Y axis would no longer let your brain rotate.
Dec
9
revised screen & xterm: how to get window split vertically in custom ratio
added 82 characters in body
Dec
9
comment screen & xterm: how to get window split vertically in custom ratio
You're right, it works! The -h option actually does what I want!! However I wanted to get the thing bigger when panes are split vertically, that's why I used -v throughout (and the window only "shook" for a moment, but it didn't really work)! I think we both have figured out the basic problem in current screen: the options are confusing as heck and far from self-explanatory. Plus, I wish someone could tell me a plausible reason why these two options for resize aren't explained anywhere in the man page.
Dec
9
comment screen & xterm: how to get window split vertically in custom ratio
No, I do want to keep using xterm because I like to stick to standard tools (for now) which work everywhere, on a home PC as well as on a workstation in the office without further tweaking or fiddling. What I can additionally install to make life easier on my private box is yet another story. But thanks for replying anyway.
Dec
9
asked screen & xterm: how to get window split vertically in custom ratio
Dec
9
answered GNU screen - Restore a session with splitted screen
Dec
5
comment How do I print '-e' with echo?
+1 Thanks, good to know to keep your scripts portable and "homebrew-Linux-independent" (i. e. also working on a pro workstation at work).
Dec
5
comment How to print new lines at the end of functions?
Well, when I got that error message on my terminal first time, I seriously thought it might be something in-between of what you pointed out. ;) Anyways...please consider that error messages from system commands may quite frequently be way off the mark, leading you up the garden path. – – In a nutshell, chances were that tr took the line as-is and parsed it for the first correct bit in it from left, which was indeed Z-A. So I thought it had read over the a- and pretended it wasn't there, just cherry-picking what it could interpret properly. (No it wasn't much.)
Dec
5
comment regarding portable sed -e… d b or ! b?
TY, cool stuff! Got them bookmarked. Gonna delve myself into those the next days for sure. BTW, please do no longer feel addressed when I say "sed learners". You definitely are no learner (LOL), more like a pro asking other uber-pros like Stéphane to squeeze out the very last quirks that remain. ;) grin
Dec
5
comment regarding portable sed -e… d b or ! b?
You're really a human hints pool! Dang, you're right, works without this ; stuff indeed. OK, to my excuse I just thought it's better to be safe than sorry. ;-) But many thanks, we're getting there. :p BUT OTOH, fiddling with this stuff in a trial-and-error fashion will usually spawn zillions of unrelated, highly-confusing error messages and warnings, so this is why I'd commonly like to avoid that at all costs.