• 1 Post
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle

  • Kind of a nothing burger.

    These repositories, belonging to more than 16,000 organizations, were originally posted to GitHub as public, but were later set to private, often after the developers responsible realized they contained authentication credentials allowing unauthorized access or other types of confidential data. Even months later, however, the private pages remain available in their entirety through Copilot.

    The repo was listed as public and archived. It’s not clear from the article but I suspect that the “private” information is just a copy of what was made public and not the information added after it was made private.








  • command! -range -nargs=1 PadColumns call PadColumns(<line1>, <line2>, <args>)
    
    function! PadColumns(start, end, columns)
        execute a:start.','.a:end.'s/\(.*\)\zs\s*$/\='.'repeat(" ", a:columns - len(submatch(1)))'
    endfunction
    

    Use by typing in Normal mode :PadColumns 20. This will add spaces after the line or selected lines to the column you specify (in this case, 20).

    You could probably improve this by getting the length of the longest line and so you dont need to specify the specific column to add spaces to (20), and instead just add say 5 spaces after longest line for all lines.


  • I do not think that this is an existing feature in neovim, however this seems to work :%s/\(.*\)\zs\s*$/\=repeat(' ', 15 - len(submatch(1)))

    Change 15 to the column desired. You could probably create a function where you pass the column number you want so that you dont have to type this string all the time.


  • mrbn@lemmy.catoLinux@lemmy.mlTIL
    link
    fedilink
    arrow-up
    28
    ·
    1 year ago

    Reminds me of the “Op” wars on IRC. All users would be given @ status and the point was to kick everyone before you got kicked. Writing scripts for this was my first “taste” at programming.





  • Have you tried setting a breakpoint and seeing if it hits? Assuming the app you are debugging is just a Console.WriteLine("Hello World"); and no breakpoints are set, the app will execute, output hello world, and terminate. Which means you wouldn’t see anything happen in VS Code.

    If you are super new to all this, I would suggest you look for videos/articles on how to debug using visual studio code as they may provide some insights or concepts you may not already know.