Activity for tripleee
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Edit | Post #283940 |
Post edited: Typo |
— | about 1 year ago |
| Edit | Post #289442 |
Post edited: Remove sudo; clarify last paragraph; fix some typos |
— | about 1 year ago |
| Suggested Edit | Post #283940 |
Suggested edit: Typo (more) |
helpful | about 1 year ago |
| Suggested Edit | Post #289442 |
Suggested edit: Remove sudo; clarify last paragraph; fix some typos (more) |
helpful | about 1 year ago |
| Comment | Post #289332 |
https://askubuntu.com/a/172689 appears to contain some useful hints. (more) |
— | over 1 year ago |
| Comment | Post #289302 |
I don't think this is a supported use case. The agent needs to run as the user whose password it is, not as `root`; and the process which talks to the agent should share a parent process with it. (I don't know if these constraints are actively enforced, but working around them would be clunky at the ... (more) |
— | over 1 year ago |
| Comment | Post #289036 |
Of course, in the general case, also make sure the file is owned by your account. (more) |
— | over 1 year ago |
| Comment | Post #289070 |
In other words, without `-p`, the first token is interpreted as a line number, etc. (more) |
— | over 1 year ago |
| Comment | Post #289136 |
See also https://linux.codidact.com/posts/289135 (more) |
— | over 1 year ago |
| Comment | Post #289136 |
Probably add details about your login manager, etc. (more) |
— | over 1 year ago |
| Edit | Post #288963 |
Post edited: Link to cargo cult |
— | over 1 year ago |
| Comment | Post #289008 |
Do you have a file named `schedule.py` or some other local file which shadows a module name? (more) |
— | over 1 year ago |
| Edit | Post #288963 |
Post edited: |
— | over 1 year ago |
| Edit | Post #288963 |
Post edited: [[:space:]] fix, thanks terdon |
— | over 1 year ago |
| Comment | Post #288963 |
Thanks, I have updated this to suggest `[[:space:]]` instead. The `-e` stuff is based on my experience with MacOS `sed`, which is sometimes wacky with `-e`. (Not at my computer so can't provide a specific demo.) (more) |
— | over 1 year ago |
| Edit | Post #288999 | Initial revision | — | over 1 year ago |
| Answer | — |
A: What unexpected things can happen if a user runs commands expecting a text file on input lacking a file-final newline? I would consider your own tools as the central use case. Seriously, do you want to litter every `while read` (or your language's equivalent) with this pesky corner case handling? ``` while read -r line || [ -n "${line-}" ] do : something with "$line" done <"$inputfile" ``` Having a sin... (more) |
— | over 1 year ago |
| Edit | Post #288963 |
Post edited: Multiple -e options |
— | over 1 year ago |
| Comment | Post #288962 |
(Also, what's `bat`? A common utility for displaying control characters etc is `cat -v`, though the only option for `cat` known to POSIX is `-u`, for unbuffered I/O.) (more) |
— | over 1 year ago |
| Comment | Post #288962 |
The use of a generator expression seems odd. You end up reading the whole file into memory anyway. Also, `b` seems redundant. Why not simply `for line in sys.stdin: print(line.strip())`? (more) |
— | over 1 year ago |
| Edit | Post #288963 | Initial revision | — | over 1 year ago |
| Answer | — |
A: Simplest way of stripping leading/trailing whitespace from file or program output The simple and obvious solution: ``` sed 's/^ //;s/ $//' ``` Many recipes you find online will erroneously add a `g` flag, but these regular expressions can only match once per line anyway. (In some more detail, `s/from/to/g` says to replace all occurrences of `from` on the current input l... (more) |
— | over 1 year ago |
| Edit | Post #288911 |
Post edited: Typo in title |
— | over 1 year ago |
| Suggested Edit | Post #288911 |
Suggested edit: Typo in title (more) |
helpful | over 1 year ago |
| Comment | Post #288849 |
My impression is that the Debian maintainers recommend switching to MariaDB. Are there scenarios where this is not acceptable? (more) |
— | over 1 year ago |
| Comment | Post #288436 |
The syntax `for item in $(command); do` is inherently broken if `command` could output items which contain spaces. There are ways to limit the damage by manipulating `IFS` but this construct is inherently brittle. See also https://mywiki.wooledge.org/BashFAQ/020 (more) |
— | over 1 year ago |
| Edit | Post #288558 | Initial revision | — | over 1 year ago |
| Answer | — |
A: Retrieve changes that closed a Debian bug https://metadata.ftp-master.debian.org/changelogs/main/p/poppler/poppler22.12.0-2changelog contains the changelog for this particular package. It should be obvious how to change to a different version or a different package. For example, https://metadata.ftp-master.debian.org/changelogs/main/e/emacs ... (more) |
— | over 1 year ago |
| Edit | Post #288556 | Initial revision | — | over 1 year ago |
| Answer | — |
A: Adding Python 3.11 to `$PATH` The usual way is to specify an installation location with ``` ./configure --prefix="$HOME/python" ``` ... and then `make install` after `make`. If you don't specify a `--prefix` argument to `configure`, it typically defaults to `/usr/local` (so `make install` will install `python` as `/usr... (more) |
— | over 1 year ago |