~vc


#234 Cannot change casing when renaming a repo 5 years ago

Comment by ~vc on ~sircmpwn/git.sr.ht

^^ That first markdown link is incorrect (my error), but the gist is still the same. Working as expected.

#234 Cannot change casing when renaming a repo 5 years ago

Comment by ~vc on ~sircmpwn/git.sr.ht

I just created a repository test-repo and successfully changed is name to TEST-REPO. Looks like the behavior is now working as expected.

#219 Content does not utilize full vertical space 5 years ago

Ticket created by ~vc on ~sircmpwn/sr.ht

Expected behavior:

The content of a page on all *.sr.ht services would fill the vertical space of the browser window. A browser window unable to render all table elements (for example repos or tickets) would use some form of paging setup as is currently in place.

Observed behavior:

Content appears to stop at X number of table elements before displaying the page selection controls, leading to display where nearly half the page is taken up by whitespace in some cases.

example

#17 Safety checks 5 years ago

Comment by ~vc on ~mcf/cproc

GCC and Clang have the options to use AddressSanitizer and UndefinedBehaviorSanitizer. Both of these act give useful diagnostic information when safety defined behavior checks are violated. It may be worth looking into optional linking of those libraries.

#234 Cannot change casing when renaming a repo 5 years ago

Ticket created by ~vc on ~sircmpwn/git.sr.ht

Discovered when trying to change a repo git.sr.ht/~vc/FGMP to git.sr.ht/~vc/fgmp.

Altering the casing of any number of letters without altering case-insensitive string of of the repository through the settings/rename tab results int the following message:

This name is already in use.

For instance FGMP -> fgmp and fgmp -> fgmP will both result in the error message displayed above.

A temporary workaround is to change the case insensitive string of the repository path, then change it again to what you actually want. For instance FGMP -> fgmp- -> fgmp.