| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
I'll refactor this if I ever need to (i.e. if I end up running X on
something other than Debian a lot).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is Debian-specific, but that's the only system with which I'm
presently using X11 anyway.
From Debian's startx(1):
> Note that in the Debian system, what many people traditionally put in
> the .xinitrc file should go in .xsession instead; this permits the
> same X environment to be presented whether startx, xdm, or xinit is
> used to start the X session. All discussion of the .xinitrc file in
> the xinit(1) manual page applies equally well to .xsession. Keep in
> mind that .xinitrc is used only by xinit(1) and completely ignored by
> xdm(1).
Indeed, everything just seems to work a bit better, probably because
problems are more likely to be able to find the user instance of dbus.
|
| |
|
| |
|
| |
|
|
|
|
| |
Syntax highlighting doesn't deal with it well
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Loaded out of order otherwise, so doesn't get set.
|
| |
|
| |
|
|
|
|
|
| |
This was closing my connection immediately when I logged in
interactively to any machine without systemd!
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is getting in the way of my work a bit too much. I'm still
learning how to use it, but throwing myself into the deep end at this
point turned out to be a bad idea.
|
| |
|
| |
|
|
|
|
|
| |
Turns out the pgrep from procps version 3.2.8 doesn't support these
longer options.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Andromeda, by Perseus sav'd and wed,
> Hanker'd each day to see the Gorgon's head:
> Till o'er a fount he held it, bade her lean,
> And mirror'd in the wave was safely seen
> That death she liv'd by.
> Let not thine eyes know
> Any forbidden thing itself, although
> It once should save as well as kill: but be
> Its shadow upon life enough for thee.
>
> --Dante Gabriel Rossetti
|
| |
|
|
|
|
|
| |
I only want to use the `||` short-circuits for control flow changes
(return, continue, break etc).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I think !-n is a little clearer, but -z is OK.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
ShellCheck (SC2164) is upset about these `cd` commands where the return
type isn't being checked, but they're all by design, as they're the last
command in the function, and thereby constitute the function's return
value implicitly.
Otherwise, this commit changes the shrc.d and profile.d subfiles to use
the `command` wrapper only where it's actually needed.
|
| |
|
|
|
|
|
| |
It's a bit silly to have this in ~/.profile; it doesn't need to be there
for such a niche case.
|
| |
|
|
|
|
|
| |
It turns out the semicolon belongs to the "in" syntax, and is optional
without it.
|
| |
|
|
|
|
| |
This is slightly more idiomatic shell.
|
| |
|
|
|
|
| |
They're nicer to read this way.
|
|
|
|
| |
Duhhhhh.
|
|
|
|
|
| |
Funtoo Linux does not include this tool by default. It's not important
enough to raise the error message on every login.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This appeases ShellCheck 0.4.7, which is fretting that I meant a command
expansion. I didn't, but it seems a bit nicer to quote these anyway.
In sh/profile.d/editor.sh line 4:
EDITOR=ed
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
In sh/profile.d/editor.sh line 22:
EDITOR=ex
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
In sh/profile.d/visual.sh line 2:
VISUAL=vi
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
|
|
|
|
|
|
|
|
| |
ShellCheck 0.4.7 complained about this:
In sh/shrc.d/tree.sh line 12:
case $opt in
^-- SC2220: Invalid flags are not handled. Add a *) case.
|
|
|
|
|
|
|
|
| |
This was originally added to cut the decryption boilerplate, which no
longer seems to be an issue; I think that --quiet may be correctly
blocking it now. Even without this, it caused more problems than it
solved when gpg(1) genuinely did need user interaction from me, for
example for --update-trustdb.
|
| |
|
|\ |
|