🐧 Lunix
-
I will be very happy to remain ignorant of your language if it ever happens.
-
If I wrote a programming language,
variable_name,variableNameandvariable namewould all refer to the same variable.Not sure if evil ideas thread or insane ideas thread...
-
Honestly, I'm okay with that (re-inventing this wheel). What does it really amount to? Most languages already have a REPL, so all the re-inventor does is wrap the language's filesystem functions. No big deal. Picking or changing your shell is trivially easy.
On the other hand, you don't want to change an existing shell, especially Bash, because a change will break millions of lines of old code for no benefit -- since you can just use a different, better shell instead.
-
If I wrote a programming language,
variable_name,variableNameandvariable namewould all refer to the same variable.But FORTRAN already exists?
-
If I wrote a programming language, variable_name, variableName and variable name would raise a syntax error if not used consistently
FTFY
-
If I wrote a programming language,
variable_name,variableNameandvariable namewould all refer to the same variable.Eeeeewwwww.
-
If I wrote a programming language,
variable_name,variableNameandvariable namewould all refer to the same variable.
The Evil Ideas thread is
-
-
If I wrote a programming language, variable_name, variableName and variable name would all refer to the same variable.
Not sure if evil ideas thread or insane ideas thread...
No, the insane idea would be changing an existing language compiler to do what @Buddy talks about, causing millions of crappy programs with poorly written variables to all shit themselves when compiled.
-
If I wrote a programming language, variable_name, variableName and variable name would all refer to the same variable.
If you do not make it a compiler error to make ambiguous variable names then that is the evilist of evil ideas ever and i would be leading the lynch mob that was hunting you down.....
because ICK!
-
At least is a step ahead of VB and SQL for being case sensitive
Also, if I might cooperate, I wouldn't call them "variables" but "containers" to avoid confusion with math ones.
-
-
But the program doing globbing has advantages too, because the program actually sees the glob. For example, do-something --to-these-files * could be made to work right on Windows, but not Linux.
The problem with that is that it opens up the possibility that the program might do something else instead, such as deciding that it wants to be a special snowflake and only work as expected if you wrap arguments in single quotes. Because. Or interpreting a leading argument that begins with a double quote as special. (I'm looking at you,
START!) Trying to write reliable code to invoke another program when this sort of thing is present is much harder than it initially appears. And of course users blame you for the fact that other programs just interact with realitythrough a fug of drugsin a non-standard fashion. They're wrong, but that doesn't make a blind bit of difference.With the Unix approach, you decide what string each argument to the program is going to be, and then you just hand that string over, separate from all the other arguments (and environment variables). That's exactly what the real OS API for launching another program takes.
-
No, the insane idea would be changing an existing language compiler to do what @Buddy talks about, causing millions of crappy programs with poorly written variables to all shit themselves when compiled.
Wait... that sounds like a good idea...
-
That sounds on about the same level, to me, as shipping a Makefile with
-Wall -Werrorincluded in the default build.(Hint: not everyone uses the same version of the same compiler. FTBFS.)
-
I HATE the argument order switchover. What the fuck where they thinking? If I'm working with service x, I might want to do
service x status, thenservice x stopthen tinker with conf, thenservice x start. With systemctl, I constantly have to edit around their stupid argument order. Also type a lot more (blah.serviceinstead of justblah).The solution is obviously to write a shell script that takes the arguments in the right order and calls the
servicecommand.
-
I know that I have, on several occasions, typed this:
sudo service start nginx start: unrecognized serviceSo the fact that I can
sudo systemctl start nginx postgresql redis-server kitchen-sinkis pretty nice. (And it'll error out of two of those have a Conflicts= relationship)
-
That sounds on about the same level, to me, as shipping a Makefile with
-Wall -Werrorincluded in the default build.(Hint: not everyone uses the same version of the same compiler. FTBFS.)
Are you implying that
-Wall -Werroris going to break on properly-written portable code?Besides, everybody knows that
-Wall -Werror -Wextrais where it's at these days.
-
Are you implying that -Wall -Werror is going to break on properly-written portable code?
I thought we were talking about
millions of crappy programs with poorly written variables
.
-
Hmm, those sound like two completely different things.
-
-
#include <stdio.h> #include <stddef.h> int main() { #ifdef ickweed printf("Hello Ben!\n"); #endif//ickweed return EXIT_FAILURE; }
-
-
Wow....
This still probably my favourite IOCCC though: http://www.ioccc.org/2013/cable3/hint.html
-
The only applications on Windows that break when you use spaces in filenames are those "ported" from Linux.
False.
Filed Under: Yes, that information actually is helpful. Congrats at doing an error message right for once MS
-
-
Meh, needed context. Sorry for the megabytes.
Yeah I could've moved cmd on to one screen and screenshotted only that screen. But that would take WORK.
-
Or perhaps a capture of the dialogue, and the top of the command window? But, as you said...
-
Rabid Racoon? Is that the latest Ubuntu release?
No way, that one is like two years old now. We're already on Vacuous Vole, with Warty Warthog (Slight Return) upcoming.
-
I'm still on Trusty Tahr. Wake me up when they release letter-that-does-not-exist-in-lojban-because-it-is-redundant.
-
release letter-that-does-not-exist-in-lojban-because-it-is-redundant
E_AMBIGUOUS_STATEMENT
-
Sorry, I mean W. Q and H are also redundant, so I should have clarified.
<no, not whooshing. Just Ben L.-ing>
-
@ben_lubar said:
letter-that-does-not-exist-in-lojban-because-it-is-redundant
E_AMBIGUOUS_STATEMENT
I'm going with Zzz...
-
If we didn't have the letter z, we couldn't spell bebzunpre!
-
If we didn't have the letter z, we couldn't spell "bebzunpre"
Or "zoozoospackle"....
-
mivdalmuzga mivdalmuzga mircai
-
This is a "we're too fucking stupid to ever examine our own beliefs and also we like our system to be harsh and difficult so we can point and laugh at new users" problem.
Pot, meet kettle. Kettle, this is pot.
-
-
> Right; but we already know it can't handle filenames that begin in dash correctly.
No, we don't. Well, I don't, and I think this falls into the realm of things you know that aren't so.
[pjh@thinkpad x]$ echo "Hello world" >> -rm [pjh@thinkpad x]$ ls -rm [pjh@thinkpad x]$ cat -- -rm Hello world [pjh@thinkpad x]$ rm -- -rm rm: remove regular file ‘-rm’? y [pjh@thinkpad x]$ ls [pjh@thinkpad x]$Not buggy, handling a file that starts with a
-, and working as intended.Not sure what colour the sky is in blakey's world this week; maybe he's been talking to too many Sasquatches...
@blakey said:
I might feel better about Linux if its proponents weren't all liars.
https://ecowomen.files.wordpress.com/2010/05/cast_iron_frying_pan.jpg
That's betterShouldn't that be either a pot (or possibly a kettle,) not a frying pan?
-
Not sure what colour the sky is in blakey's world this week; maybe he's been talking to too many Sasquatches...
I assume he was just misremembering how he misunderstood @cartman82's problem with
~expansion in the shell. But we may never know.
-
The sound of a cast iron frying pan meeting a forehead at speed needs to be heard at very close range for its full beauty to be appreciated.
Here, let me show you it.
-
There's a, well… magic incantation you can put at the start of a filename to make it use the route without the filename size limit. (I have to look it up every time; it's not obvious.) When they're running on a capable platform (i.e., pretty much all the time; this is 2015, everyone!) the runtime could just add that at the front in the correct way and route around the problem automatically.
I don't know why they don't. (I have my suspicions, but it's Easter so let's not cast too many aspersions…
)
Bah, don't be so proud of your ignorance.CreateFileW ("Unicode version of CreateFile) and its various Unicode friends that use file and/or path names all handle names with up to 32767 Unicode characters (plus an L'\000') instead of MAX_PATH (260) characters including the trailing NUL.
To do this you must:
- Normalise the name. That is, it must be an absolute path without ..\ elements, with all / separators replaced by the canonical , and with all repeated separators replaced by a single one. It must be usable directly with NO conversion, expansion, substitution, and whatnot.
- Preconcatenate it with '''\.''' (''' meaning string with no quoting by , so the pre-token is backslash-backslash-dot-backslash.)
E.g.
C:../////fribble.txt, if%PWD%isC:\this\thatmust be rendered as\\.\C:\this\fribble.txt
E.g.\\server\\share\\this\that\the other.txtis rendered as\\.\\\server\share\this\that\the other.txtThis works on Win32, not just on the underlying NT API, and requires any version of the NT family, I think. Certainly it works on Win2000.
-
Look at who started the thread.
You can look up words here: http://mw.lojban.org/extensions/ilmentufa/i/en/
-
Not buggy, handling a file that starts with a -, and working as intended.
Already mentioned above. "Can be made to work" I think isn't the same thing as "works"; the way it works on Linux is error prone and the easy thing that you almost always see (using*instead of./*, or at least not always using--) is an incorrect thing to do by default.
-
Linux is error prone
Yes, but saying that the design is error prone, but if you follow the rules, it works is not the same as saying it doesn't work.
-
2. Preconcatenate it with '''\.''' (''' meaning string with no quoting by , so the pre-token is backslash-backslash-dot-backslash.)
You got DiscoMarkdowned.@"\\.\"
-
@"\\.\"body is invalid
-
For example, on this install I unchecked the "Desktop environment" package during install, rebooted to shell, and installed what is considered a non-standard Desktop environment for Debian.
There is an easy way to do it :
To select the desktop environment that the debian-installer installs, enter "Advanced options" on the boot screen and scroll down to "Alternative desktop environments"
-
Huh. TIL.
Well, anyway, it works now :P
-
Languages in which whitespace is significant - Everything2.com
