GARTHWILSON wrote:
...
Here's my first problem with it. Someone gives the link to their repo, and you see the first level of the file tree. The lines there have file names and folder names, but don't tell you what any of them are. Where you'd expect a description to the right, it only tells you what the last edit was for.
Well, I don't really see that so much as github's fault per say, git doesn't collect information on what a file is for; it only collects the change comments.
I don't know of any revision control that does collect that kind of information. (Maybe one does? :shrug:)
While I could see that being a useful feature in a revision control system, I do wonder how many developers would actually use such a system seeing that many (especially today) seem to be completely adverse to writing documentation about their code.
Github could certainly add something like that to their interface, though it would have to be done outside of git. As, like I said, git doesn't collect that sort of information about the file.
TL;DR: You're really at the mercy of the developer if they decide to provide a source code map or something.
Quote:
So I stab a guess and pick a line that might be what I'm looking for, and it leads to another level with more files or folders listed, and the problem repeats. I go down the various branches...oops, no, that's not it...back up...try this one... nope, that's something else...How 'bout this one?...again, no... back up...and so on. After many minutes of this, I give up. I have access to the 6502.org github, and I have a similar problem, even though by now I should be familiar with it. Even when I know the name of a file to do a search for (which I never do on someone else's repo), I still often have trouble, and I have to email Mike and ask for a link.
The file navigation can be a bit tricky, especially if you get lost in different branches of the code.
I've never really used the per file search in Github as it tends to get overwhelming fast as it is actually searching way more than I want it to. Hence why I just clone the code, and search it with the more familiar Posix and Windows tools I have at my disposal.
Quote:
Then when I do get to someone's source code, I hate the way it's shown. I want black text, not gray, not multi-colored, with column 1 on the left, ie, no line numbers there (they should be in a footer bar telling where you've placed the cursor) and no other space. There should be no line wrap in source code. If a line is really long, I'd rather do side-to-side scrolling or just turn the font size down enough to get the whole line in the window. I could download it and use a different text editor or something, but I shouldn't have to download all this stuff to look at it once and try to answer a forum question.
Attachment:
shot1.png [ 80.68 KiB | Viewed 2748 times ]
*click*
Attachment:
Screenshot 2024-02-23 154056.png [ 189.92 KiB | Viewed 2748 times ]
All that aside, how you want to see the code formatted is going to be different from the next person, so there's no one size that fits all here. My best suggestion is again, clone the source code, open it up in your editor/IDE of choice where you have a lot more control over how it's presented to you.
I mean, at this point we could get into the details about how different people like to tab and space their code for formatting. I guess I don't see that as a big deal as I can just download the code and run it through a program like astyle 99% of the time and get it into a format I can read.
Quote:
Now github wants 2FA, and none of the 2FA options it offers are acceptable to me. The preferred one would be that it send me an email with a one-time-use access code, like other sites do. Another possibility is calling me with a voice message of such an access code. Those are not options though. I do not, and will not, use a smartphone or buy other equipment. Fortunately logging in is not required to view someone else's repo though.
That being said, the lack of an email option is totally on Microsoft. (They should at least offer the option to send the code via SMS which can work with any basic cell phone, not just smart phones)
Given my anger at how they treat the logins on people's personal machine I could get on a huge soapbox about how I detest some of the "security" decisions about what Microsoft does. But this isn't the place for such.