This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-07
Channels
- # announcements (1)
- # architecture (9)
- # babashka (3)
- # calva (10)
- # clj-http (13)
- # clj-kondo (11)
- # clojure (23)
- # clojure-europe (11)
- # clojure-nl (1)
- # clojure-norway (112)
- # clojure-uk (4)
- # clojuredesign-podcast (8)
- # clojurescript (10)
- # core-async (5)
- # cursive (7)
- # data-science (15)
- # datascript (2)
- # datomic (29)
- # emacs (5)
- # events (1)
- # hugsql (1)
- # hyperfiddle (9)
- # midje (1)
- # missionary (3)
- # music (1)
- # off-topic (34)
- # polylith (1)
- # re-frame (16)
- # shadow-cljs (117)
- # squint (19)
- # yamlscript (1)
is it possible to create a folder named literally .
?
(not implying that this is a good thing to do or that I need it, just … curious. mkdir .
claims that .
exists, but I want a new folder in .
with the name .
.)
I am pretty sure it's impossible as .
is the equivalent of here
in POSIX systems...
YMMV
$ mkdir --file
mkdir: illegal option -- -
usage: mkdir [-pv] [-m mode] directory_name ...
$ # but we can get around these rules!!!
$ mkdir -- --file
$ ls
--file dot
I guess that if you really wanted to be able to do it you could consider forking a linux distribution and making some very low level changes so that another character, say ^
means here
and then you could use .
to your heart's content, but honestly I would not know where to start.
So …
If I create a folder named .
on this custom linux distribution, tar it into an archive and extract on my normal computer, it would … presumably crash on trying to extract?
I would love to say that I am going to write a custom linux distribution to try this out, but I am afraid I won’t be able to do that today. Thanks for the replies --- I didn’t imagine that this was an OS-wide assumption, I just assumed it was a bash/zsh-thing!
No worries - I think that you would need a custom shell as well, but I think it's baked into the OS; I could be wrong about that.
if you have a folder named .
you can't do something like ./run.sh
if run.sh
is in the current directory... and that is the way to do. and thinking about, you already have a dir names .
the one you are in. so you can't create another one with that name.
maybe on some really obscure non posix file system you can get some thing different... but then you'll have to run it on a OS/390, OS/400, HP3000, CTOS or any other obscure OS maybe?
don't think so... as I can remember you can do cd..
on a window/dos terminal.. so I suspect .
to be there as well
I am fairly sure that on Unix/Linux, "." is effectively automatically created in every directory when the directory is created, and cannot be renamed. Also ".."
I would be very very wary if you somehow renamed them of what kinds of software would go horribly wrong afterwards.
The assumption of what those names mean is deeply embedded in lots of places.
If all you want is a tar file with a folder named .
there is no need to create a custom linux distro. The .tar file format is presumably simple enough that you can just write a small program to create that, maybe even a hex editor suffices.
I was thinking of replacing a :txn-fn
/ :rollback-fn
name pair (for a Saga-like pattern) for a shorter name pair that, fun requirement, should have the same character length (so that map alignment is always produced).
Any cool/creative suggestions?
cmmt/abrt