On Sep 16, 2013 4:50 AM, "H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote:
>
> On Mon, Sep 16, 2013 at 04:04:24AM +0200, Adam D. Ruppe wrote:
> > On Monday, 16 September 2013 at 01:48:31 UTC, H. S. Teoh wrote:
> > >Have you ever tried to configure sloppy focus on Windows?
> >
> > yup. It kinda works until you get the idiot apps that raise themselves whenever they get focus! Which are a lot of them. Ugh.
>
> Exactly. A major annoyance when you're trying to type something while looking at something else in another window for reference.
>
>
> [...]
> > >Heh. I just use 'bg', 'jobs', and 'fg' on a single terminal. :)
> >
> > Yeah, I do that sometimes too, but you can get output mixed together! And you can't easily watch for updates without that. So I like to use windows and gnu screen. The windows actually come and go, as I just reattach a running screen session when needed.
>
> GNU screen is pretty awesome. But it has some warts that makes me not use it by default:
>
> - Its default escape sequence is extremely annoying (ctrl-A clashes with
>   bash's go-to-beginning-of-line, which I use literally *all* the time).
>   Switching it to something like ctrl-U makes it more tolerable.
>
> - It doesn't seem to pick up terminal settings correctly sometimes.
>   Which results in needing to set $TERM manually, or type
>   `TERM=rxvt-unicode program args`, instead of just `program args`.
>   Quite annoying.
>
>

Someone did suggest an alternative to GNU screen that is being actively developed on (GNU Screen is kinda regarded as unmaintainable) but I forget the name of it.

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

On Monday, 16 September 2013 at 07:43:15 UTC, Iain Buclaw wrote:
> Someone did suggest an alternative to GNU screen that is being actively
> developed on (GNU Screen is kinda regarded as unmaintainable) but I forget
> the name of it.
>
> Regards

tmux?

On Monday, 16 September 2013 at 07:39:29 UTC, Iain Buclaw wrote:
> For some reason I use /opt/usr or /opt/${appname}
>
> Regards

As far as I understand, "/opt" is recommended by FHS for such stuff.

On Monday, 16 September 2013 at 01:55:25 UTC, H. S. Teoh wrote:
> On Sun, Sep 15, 2013 at 07:14:17PM +0200, Dicebot wrote:
>> On Saturday, 14 September 2013 at 10:32:26 UTC, Nick Sabalausky
>> wrote:
>> >My understanding (purely from the link below) was that /usr/local/*
>> >was *specifically* for non-package-managered stuff, whereas /usr/*
>> >was *specifically* for package-managered things:
>> >
>> >http://unix.stackexchange.com/questions/8656/usr-bin-vs-usr-local-bin-on-linux
>> 
>> Not entirely true. You should never have anything not managed by
>> package manager on Linux system, it is a reliable road to disaster.
>> Better distinction is "/usr/" for packages from official repos,
>> "/usr/local" for own custom packages.
>
> Seriously? I installed unmanaged stuff all the time, and never had much
> of an issue. Though, granted, I never put them under /usr or /usr/local
> at all. It's usually in a dedicated subdirectory under $HOME.
>
> Installing unmanaged stuff under the /usr tree is tricky business,
> because when you're trying to *uninstall*, you usually don't remember
> where all the bits have been scattered, and leaving them lying around
> can lead to trouble.
>
>
> T

Ever since watching a friend have his entire /usr deleted by a dodgy 'sudo make install', i desperately avoid manually installing to anywhere but a dedicated subdir in $home. No root access needed and I actually know where everything is =)

On 16 September 2013 08:58, Dicebot <public@dicebot.lv> wrote:
> On Monday, 16 September 2013 at 07:43:15 UTC, Iain Buclaw wrote:
>>
>> Someone did suggest an alternative to GNU screen that is being actively developed on (GNU Screen is kinda regarded as unmaintainable) but I forget the name of it.
>>
>> Regards
>
>
> tmux?

That sounds about right,

-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

On 16/09/13 07:01, deadalnix wrote:
> What do you use to do that in vim ? All my attempts did fail.

I use this plugin: http://www.vim.org/scripts/script.php?script_id=231

It's always worked for me.

On 15/09/13 22:49, Nick Sabalausky wrote:
> I love that comic!

Me too :-)

> I actually did the same tab/space thing for awhile. But my editors
> didn't really have a native understanding of it so it became manual
> editing of invisible characters, so now I just avoid that style of
> alignment regardless of tabs or spaces. Ie, instead of:
>
> foobar(aaaaa, bbbbb, ccccc,
>        ddddd, eeeee, fffff);
>
> I'll just do:
>
> foobar(
>      aaaaa, bbbbb, ccccc,
>      dddd, eeeee, fffff
> );
>
> Not as pretty, but it works, it makes things simpler, Plus it avoids
> the former style's tendency to wind up with gigantically-sized indents.

It's true, the former indentation style can be really annoying if it forces you to indent by too much, especially if it clashes with a code style that prefers line lengths of less than a certain number of characters.

I still prefer it to your alternative way of doing things -- I find that creates confusion between the opening and closing parentheses of functions and opening and closing braces of scopes, but that's partly a matter of taste and familiarity, and it clearly does have benefits.

On Monday, 16 September 2013 at 08:07:23 UTC, John Colvin wrote:
> Ever since watching a friend have his entire /usr deleted by a dodgy 'sudo make install', i desperately avoid manually installing to anywhere but a dedicated subdir in $home. No root access needed and I actually know where everything is =)

I always create PKGBUILD's for stuff I need to install. Event it is a tiny one shot thing. And the fact that it automatically will run install script in contained sandbox is one of the major decision factors here (even placing in $home can destroy your home if makefile author is sloppy enough)

On Monday, 16 September 2013 at 10:10:32 UTC, Dicebot wrote:
> On Monday, 16 September 2013 at 08:07:23 UTC, John Colvin wrote:
>> Ever since watching a friend have his entire /usr deleted by a dodgy 'sudo make install', i desperately avoid manually installing to anywhere but a dedicated subdir in $home. No root access needed and I actually know where everything is =)
>
> I always create PKGBUILD's for stuff I need to install. Event it is a tiny one shot thing. And the fact that it automatically will run install script in contained sandbox is one of the major decision factors here (even placing in $home can destroy your home if makefile author is sloppy enough)

Seeing as I'm typing this from my newly set-up Arch64 installation, I suspect I might go down that route too =)

Btw, compltely off-topic, do you have any recomendations for an AUR helper?

On Monday, 16 September 2013 at 10:35:08 UTC, John Colvin wrote:
> On Monday, 16 September 2013 at 10:10:32 UTC, Dicebot wrote:
>> On Monday, 16 September 2013 at 08:07:23 UTC, John Colvin wrote:
>>> Ever since watching a friend have his entire /usr deleted by a dodgy 'sudo make install', i desperately avoid manually installing to anywhere but a dedicated subdir in $home. No root access needed and I actually know where everything is =)
>>
>> I always create PKGBUILD's for stuff I need to install. Event it is a tiny one shot thing. And the fact that it automatically will run install script in contained sandbox is one of the major decision factors here (even placing in $home can destroy your home if makefile author is sloppy enough)
>
> Seeing as I'm typing this from my newly set-up Arch64 installation, I suspect I might go down that route too =)
>
> Btw, compltely off-topic, do you have any recomendations for an AUR helper?

I got used to yaourt when it was basically the only option :) I don't even know what others are to be honest P)