assembla | Python wrapper for assembla 's API | REST library

Just use ::before, and ::after pseudoselectors

You can use a different svn client (example: TortoiseSVN, or cmd-line) to set the password. All SVN Clients share the same stored password mechanics. You can also remove the stored password(s) by accessing the saved passwords which are available under %APPDATA%\Subversion\auth\svn.simple removing the files inside will make SVN tools "forget" your passwords.

Here's my solution to the problem. It would be preferable to carry this out with CSS, but the constraint of not changing around the HTML made that impossible (as far as I can tell).

A few things to note: You're using a JQuery plugin which you've just copied and pasted here. As it turns out, this was rather fortuitous because I had to fix a problem with the plug-in itself. I needed the begin callback to be passing the element being clicked on, but it wasn't doing this, so I added it in. This means though that this solution wont work with the OnePageNav plug-in as it stands. I personally don't think it matters if you just import it into your own code because it isn't very big, and also it doesn't seem to be maintained anymore, so there probably wont be any more releases of it anyway.

I've also edited your code quite a bit in order to remove things which weren't relevant to the problem in hand to make it easier for me to understand. I also want to the solution to be as general as possible so that other people might be able to benefit from this too. I've kept the 'spirit' of your code though so I don't think you should have any problems should you want to adopt this solution.

It's more than likely because the files are getting an EOL-format change. Why? It could be because the developers are not being careful with that (IDE messing them up?)... or, most likely, that you have set up git to change EOL format of the files (core.autocrlf rings a bell?). You can still see through those revisions using git blame -w. My best advice: rewrite history of the branches so that the EOL format never happens (it has a price tag.... in terms of effort, just in case)... and do not set up git to change eol formats.

PS I am writing a guide on how to deal with conflicts and I am currently working on a script to be able to, kind of painlessly, rewrite the history of a branch so that the EOL format changes are corrected.... but it will be ready in a few days till I release it. I can write an update here if you want. The guide is here http://www.ezconflict.com/ (no tracking, no monetizing).

PS2: Script to correct EOL changes. It assumes (actually checks) that what you are asking to correct is a straight branch, no merges. Provide the last revision that had correct EOL formats, the tip of the branch (branch name, or revision) and the list of files that need to be corrected.

https://github.com/eantoranz/conflict_book/blob/main/scripts/correct_eol.sh

By the way, still hot from the oven. Use with caution (it won't move any branches, just in case).