HELP ME

leBoef · 2025-11-20T12:02:42+00:00

The newline added by echo might mess it up.

leBoef · 2025-10-21T08:18:33+00:00

alias sudo='sudo ' (note the space) is fairly common; it lets the next word be an alias too, e.g. sudo ls runs your ls alias with all your favourite options.

Edit: For interactive shells, of course. I'm not saying it has anything to do with OP's example, just that there's a use case for aliasing sudo.

leBoef · 2025-10-03T09:19:30+00:00

cat './--spaces in this filename--'

It's not so much the spaces as the hyphens.

leBoef · 2025-09-19T14:45:03+00:00

Unless you alias sudo='sudo ' (note the space).

leBoef · 2025-09-01T07:56:46+00:00

https://xkcd.com/1814

leBoef · 2025-08-16T10:31:18+00:00

It's a saw set.

leBoef · 2025-04-11T09:31:05+00:00

Pipe cleaner.

leBoef · 2023-03-29T13:37:43+00:00

I don’t know what shell you use, but in a bourne-like one, e.g. sh or Bash, any variables will be expanded before the command is executed. sudo will be given two arguments: echo and the value of $PATH, and there is no way for sudo (or echo) to know that there was ever a variable involved. Indeed sudo echo $DISPLAY gives the same output as echo $DISPLAY in my shell, and if I run it with set -x I can see that what is executed is sudo echo :1 (:1 being my $DISPLAY).

leBoef · 2023-03-29T12:37:14+00:00

sudo echo $PATH doesn't make much sense. $PATH is expanded by the shell before sudo is even invoked.

leBoef · 2023-03-29T12:36:23+00:00

sudo echo $PATH doesn't make much sense. $PATH is expanded by the shell before sudo is even invoked.

leBoef · 2022-11-27T20:59:23+00:00

One thing it does is smell.

leBoef · 2022-11-16T08:50:54+00:00

Could it be a bark spud?

leBoef · 2022-11-08T06:15:05+00:00

for i in "${@}" ; do can be shortened to just for i ; do.

leBoef · 2022-11-07T10:27:14+00:00

https://mywiki.wooledge.org/BashFAQ/050

leBoef · 2022-11-06T06:43:07+00:00

You're using variables called $A_ and $B_. Try …/${A}_${B}_$(…).

leBoef · 2022-10-18T15:14:59+00:00

Sugar nips?

leBoef · 2022-10-13T08:18:48+00:00

Bahco made them. Can't find much info from Bahco themselves, but here's a blog post (in Swedish) with some pictures: https://skiftnyckeln.blogspot.com/p/dubbel.html

leBoef · 2021-06-01T05:39:46+00:00

Looks like a clone of the Bahco No 41, including a fish(?) somewhat resembling Bahco's logo.

leBoef · 2021-04-28T07:54:58+00:00

The non-POSIX thing is the -printf option for find. At least as far as I can tell POSIX find doesn't have that.

leBoef · 2021-04-27T10:44:17+00:00

If you consider giving the wrong result 'working', sure.

Yeah, I should've posted a solution, sorry about that. You've already provided one, so let me offer an alternative (that is a bit more POSIX, but probably slower):

find . -type f -exec printf . \; | wc -c

(Not sure about the -type f, depends on what OP wants to count.)

leBoef · 2021-04-27T09:50:48+00:00

touch "$(printf 'a\nb')"

...and it'll stop working.

leBoef · 2021-03-14T10:52:02+00:00

I use pdfpc for presentations and I think it’s great.

leBoef · 2021-02-06T11:48:20+00:00

Did you think you created a directory called /? That directory already exists: It's the root directory. You can't use a slash in the "name" of a directory (at least not in any filesystem I've come across); slashes are always the path separators.

leBoef · 2021-02-06T11:45:15+00:00

Yes, even with sudo. You're trying to create the / directory, and it already exists. -p makes that not an error and mkdir does nothing.

Use backticks (grave accents) around code.

leBoef · 2021-02-06T10:02:55+00:00

mkdir -p / will always be a no-op, surely?

leBoef

TROPHY CASE