More stupid Git errors THIS TIME IN FIRST-PERSON!
-
"rm -fr" would work on Linux, OSX, FreeBSD, pretty much every OS out there except on you #%&@ Windows, so just make your brain work a bit (if that is possible) and translate the damned instruction yourself
They went out of their way to make it difficult.
They could have just said, "delete this path: c:\blahwhatever"
But no, instead it tries to "guess" what syntax your OS has for deleting paths, WITHOUT TELLING YOU THE THING YOU NEED TO DO IS DELETE THE PATH!
-
They went out of their way to make it difficult.
Actually they probably didn't. When it was written it made sense on the target platform. Then someone else ported it and didn't go out of there way to change the message.
-
Actually they probably didn't.
Yes they did. They told you what syntax to type instead of what operation to perform. In what world is the first better than the second?
-
It's the only answer when the question requires things to be true when they aren't.
Mu
-
Yes they did. They told you what syntax to type instead of what operation to perform. In what world is the first better than the second?
I mean. If it's the right syntax then aren't they going out of their way to be helpful? Then you don't even have to type it, it's already right there.
-
I mean. If it's the right syntax then aren't they going out of their way to be helpful?
THE MAN HAS EATEN HIS FISH BUT HE DOES NOT KNOW HOW TO FlSH
-
What if? Are you actually asking? Because it does run in cmd. Just about as horribly as anything else does. But it does.
rustcandgreprun just fine. Git doesn't. It even issues warning "terminal not fully functional" on some commands (those where it is a problem).Yes they did. They told you what syntax to type instead of what operation to perform. In what world is the first better than the second?
In case you're clueless idiot. Instructions should be as simple as possible, right?
-
THE MAN HAS EATEN HIS FISH BUT HE DOES NOT KNOW HOW TO FlSH
It seems to me the chances of someone not being able to understand that message, using CLI Git on a platform that uses 'rm' to remove things are vanishingly small. Especially compared to the vastly more people who understand it fine and can just click on it to run the command right away.
Also I thought you didn't want to have to learn how to fish?
-
rustc and grep run just fine. Git doesn't. It even issues warning "terminal not fully functional" on some commands (those where it is a problem).
I believe you. I guess I just haven't run into any problems yet.
-
Also I thought you didn't want to have to learn how to fish?
I love fishing but I really don't like eating fish. Honestly, they smell less offensive on the boat than after they've been cooked.
-
I love fishing but I really don't like eating fish. Honestly, they smell less offensive on the boat than after they've been cooked.
World's best fishing buddy detected.
-
I believe you. I guess I just haven't run into any problems yet.
You never had to usegit log?
-
You never had to use git log?
It seems to be working. What should I be looking for exactly?
-
A warning that's getting printed, and beeping when you try to scroll?
Just to be sure - you are running bare cmd.exe, without any additions or customizations, right?
-
A warning that's getting printed, and beeping when you try to scroll?
Just to be sure - you are running bare cmd.exe, without any additions or customizations, right?
No warning. Only beeps when I try to scroll past the ends.
I didn't even know you could customize cmd. Unless that's what the Git-for-Windows installer did when I checked the box for "Use Git in Git Bash and in CMD" or whatever it says. I figured that probably just put something in an environment variable.
-
Unless that's what the Git-for-Windows installer did when I checked the box for "Use Git in Git Bash and in CMD" or whatever it says. I figured that probably just put something in an environment variable.
I'm pretty sure it just updates PATH.
-
Well, during install I selected "bash only" or whatever it's called, and just for testing purposes ran cmd, added git to path and messed around. Might be that I haven't put Cygwin in path. Iunno. Whatever. I'm using TortoiseGit anyway.
-
So when asked if you want it to run in CMD you said "no." And then you forced it to run in CMD anyway. And it didn't work very well.
Stop the presses.
-
But if my little ad-hoc hack didn't work, it means cmd had to be modified somehow to be usable with git...
Also, I tend to not use stuff that's not recommended - and installing git for cmd is clearly marked as such...
-
Does it? Maybe if you check the box it modifies Git to run outside of Git Bash? And maybe it doesn't modify cmd. Hell if I know.
The disrecommended option is to install all of the *nix commands so they run in cmd. That's the third box. I'm talking about the second box.
-
Note that the middle option is for running Git via Cygwin. I was speaking of the last one.
-
BTW I always found it funny that some people use
-rfand others-fr. Kinda like on which side you put space in C pointers.I use
-Rf. According to a Facebook test I once took that means I have an outgoing personality and look good in green.
-
-Rf
Disappointed to see that argument is case insensitive. I wouldn't have been surprised if
-RmeantMove files into a Recoverable recycle bin instead of deleting
-
It is case sensitive. It's just that both cases do the same :P
-
Note that the middle option is for running Git via Cygwin. I was speaking of the last one.
Not exclusively. I don't have Cygwin and it still works.
Are you saying choosing the 3rd option makes
git logall wonky?
-
No, choosing the 1st one does. 3rd is marked with red warning sign.
-
Alright then.
-
Oh, it's one of those ones where you're meant to be psychic rather than using the most common expansion of an acronym. Gotcha
Sure, if you're from the 1930's...
-
-
WC is pretty much international. Or at least international in Europe.
-
This post is deleted!
-
@Adam_Richard said:
Binary options merging carries a high level of risk and can result in the loss of all your data. You must be aware of the risks and be willing to accept them in order to deliver your products. These are not mere words because I have proofs to how I achieve no conflicts at binary merges and I am writing to share my successful shell scripts with @Blakeyrat!
FTFYAlso - WTF, a spambot on Discourse? Shouldn't that be, you know, impossible?
-
spambot on Discourse? Shouldn't that be, you know, impossible
We get them from time to time.
Rarely of course, buy they are around
-
...should I or shouldn't I...
-
Sure, go for it.
Filed under: Should you or shouldn't you what?
-
Rarely of course, buy they are around
You keep using that word. I don't think it means what you think it means. At least the context you used it in suggests so.
-
...... frack. and i was on mobile too for that one.
-
No problem. I think there's some miscommunication here, as you mentioned a pre-commit hook, which I took to mean that this hook would execute locally. I think that the hook that both of us have in mind, is called post-receive in Git.
-
yeah. In SVN it'd be precommit: before the canonical repo receives the change. Maybe... does git have like, pre-push?
-
Pre-push is also local, but git does have pre-receive and update server hooks.
-
[quote="antiquarian, post:342, topic:49928"]
If @wood said Discourse was meant for programmers, would that excuse Discourse's UI failures?It is for programmers. And everybody else. And Discourse has no failures, it is too big to fail.
-
Saved somewhere on my path as
git-up:#!/bin/sh git stash && git pull -r && git stash popSo now I can run
git upfrom the commandline and have semi-sane update behaviour (although you can still occasionally get mergescrewed from time to time). Of course, it means I have to drop to the commandline if I want to update, but I'm usually building from the commandline anyway, so it's only really a big deal if I need to update prior to committing or pushing from a GUI...
-
I have this in my .gitconfig:
[alias] d = diff --staged HEADThat way, I can type
git dand it'll tell me what I'm about to commit.
-
i'll have to remember that one.
i personally use: PyGitUp because it auto rebases for me across all local branches and i'm not installint the original ruby based git-up because ruby
it's also available on windows (with a little work) unlike ruby because ruby on windows = fuck you apparently
