4 ms·
I might say that allowing spaces (newlines, quotes, asterisk , and various other "control" characters) in the filenames is the real bug. Sure its cool that you
by StillBored 7y ago
I might say that allowing spaces (newlines, quotes, asterisk , and various other "control" characters) in the filenames is the real bug. Sure its cool that you can put anything you want in a filename, but do you really need them? Particularly on a command line oriented OS? If the entire OS's experience was windows explorer style interactions or C binary strings like manipulation then fine.
This causes nothing but problems, all to avoid a simple character filter..
https://www.tecmint.com/manage-linux-filenames-with-special-characters/ https://www.tecmint.com/manage-linux-filenames-with-special-...
See how many "errors" you can find in that article. There are a bunch, consider the touch *, example if your using rm...
- joshuaissac 7y agoA space is a completely normal character that users quite reasonably expect to be able to have in filenames. Treating it as a regular character is not a bug. There are lots of Linux programs that can deal with spaces in filenames already.
- orev 7y agoAt this point that ship has already sailed. And it’s really not that unreasonable for users to want to be able to use what is available to them on the keyboard.
- kortex 7y agoI really wish there were a "lexical space" (spacebar) and "semantic space" (shift-space or some other control). Use something less obtrusive for the semantic space than - or _, like the interpunct ·. It breaks visually/semantically but is lexically part of the same string. this·is·variable·one Vs one two three Now I just use an ergodox ez (qmk-driven) keyboard with _ in an easy spot and snake_case everything but people says it's "ugly" or some bs (camelCase, especially with initialisms, drives me nuts).
- Izkata 7y agoSpace (%20) and non-breaking space (%A0). People do somehow type the second one into web forms regularly enough (resulting in strange error messages) that those two hex codes are embedded in my brain.
- DonHopkins 7y agoI like to put U+00AD aka aka ­ invisible soft hyphens into my long file names and variable names, so they break correctly when displayed in formatted text. https://en.wikipedia.org/wiki/Soft_hyphen https://en.wikipedia.org/wiki/Soft_hyphen MargaretAreYouGrievingOverGoldengroveUnleavingLeavesLikeTheThingsOfManYouWithYourFreshThoughtsCareForCanYouAhAsTheHeartGrowsOlderItWillComeToSuchSightsColderByAndByNorSpareASighThoughWorldsOfWanwoodLeafmealLieAndYetYouWillWeepAndKnowWhyNowNoMatterChildTheNameSorrowsSpringsAreTheSameNorMouthHadNoNorMindExpressedWhatHeartHeardOfGhostGuessedItIsTheBlightManWasBornForItIsMargaretYouMournFor.txt
- kortex 7y agoNeat! I'm gonna try both of these in my workflow.
- DonHopkins 7y agoNews flash: it's not 1975 any more. Real human beings use computers, and name files, all by themselves. Some real human beings even have apostrophes and spaces in their names, which they often like to use in the names of their own files. Welcome to the future.