Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

> journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there

Yeah, this is a bit of an odd complaint. If I were this bothered by having to type those, I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.



sort by: page size:

> The unordered list markup symbol is a dash -. The other two Markdown options are * and +. But * is ambiguous and + is unpopular and there must be one way only!

THANK YOU for getting rid of the asterisk. As a former org-mode user it has always bugged me when people use the asterisk for lists, not headings. :)


argh trailing slashes can be a pain! I've had to delete/move many times due to differences in trailing slashes.

> Looks like Microsoft messed up the line breaks on switching to a new blog platform.

One could argue Microsoft has been messing up line breaks since 1981.


I'm constantly annoyed that normal cp _doesn't_ support the trailing slash distinction. It's so useful.

> Most word processors have underline as separate from underline.

One of those words isn't supposed to be 'underline', right?


Ha, yes, that is annoying actually! Instead it adds a kind of arrow-shaped bullet point. I always wondered why.

Yeah the trailing slash cargo cult just goes to show the author has no idea what he/she is doing. Even more pointless is a pretentious space before the slash. It appears many extant uses of the bogus slash result from WordPress filters and their fragile nature (never change a running WP system aka WP trainwrecks) rather than manual insertion.

I've never heard of this. When / how / why would you use the trailing dot? I checked my sites and they redirect to the non-trailing version. Is that bad?

That's not what the - operator is supposed to do. It's supposed to suppress pages containing the keyword after the -.

> Well, these browsers "helpfully" fix the URL to change backslashes into regular forward slashes, I suppose because people sometimes type in URLs and get their forward and back slashes confused.

More likely because Windows has historically used \ rather than the / that's standard in Unixish systems. Windows people are used to typing \, so it's indeed somewhat helpful for the browser to accept either (e.g., in file:// URLs).


They still have a point, though. There are virtually no platforms that don’t support forward slashes, yet there are abstractions in place to avoid simply using slashes. This may be irrelevant, but it’s still a useless layer of complexity.

The trailing slash seems to be a typing error.

> I'll remember asterisk in the future.

Aaand you've just learned all the formatting HN has :). That, and URLs automatically turn into clickable everywhere except the body of a self-submission (i.e. submitting a text instead of a link). Any other formatting here is just convention.


How is using forward slash less unnecessary than using backslash? So much more so that it needed to be pointed out without prompting?

I mean backslash is the canonical path separator on Windows, so pointing out that one could use something else was helpful how?

> You either refuse to understand, or you understand and refuse to show it

I actually don't understand the motivation for the comment at all.


> the users had, instead of altering the formatting appropriately, removed this automatic numbering, because Microsoft Word doesn't make these sorts of distinctions clear and explicit.

You can get into much worse situations than this once you leave the "happy path" in LaTeX.


I suggested slash zero in an issue and some rando mentioned dotted zeroes serve the same purpose. So annoying.

trailing slash works and is easier to type ;)

> Except that the same coworkers are wont to include trailing whitespace or omit the final newline

Editorconfig[1] makes this a non-issue.

[1]: https://editorconfig.org/


That seems unfortunate, since my shell's autocomplete puts that trailing slash in there by default.
next

Legal | privacy