home.social

#filename — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #filename, aggregated by home.social.

fetched live
  1. Can anyone point me to an online Java compiler which runs the JDK on Windows? I only find Linux systems.

    I would be particularly interested in what

    java.nio.file.Path.of("a/b/c")

    returns on a Windows system. My hunch is that it is the same as

    java.nio.file.Path.of("a\\b\\c")

    because the forward slash, afair, also works as a path separator. Or is the forward slash merely a no-go character like ':' and many others?

    #java #windows #filepath #filename

  2. in der Datei /lib/thunderbird/omni.ja
    die Datei chrome/messenger/content/messenger/mailCommands.js

    Zeile 548:
    function GenerateFilenameFromMsgHdr(msgHdr) {

    (Code in Alt-text)

    #Opensource #Thunderbird #EML #JavaScript #Filename

  3. I believe #GitLab issue gitlab.com/gitlab-org/gitlab/- is important (not top-prio, but still important), but can't really put my finger on why. Can you help me come up with reasons so I can comment arguing for it to be reopened (and hopefully fixed)?

    Maybe @yournameisinvalid can help? The #bug is about #fileName​s, not names of people, but I suspect there might be some overlap.

    I'd refer to @spolsky's joelonsoftware.com/2003/10/08/, but I fear that might come across as condescending, which isn't my goal.

  4. #Development #Reviews
    New TLDs: not bad, actually · Why the debut of .zip and .mov as top-level domains has caused a stir ilo.im/12x3fe

    “The level of fear-mongering about .zip and .mov is just comical.” — Eric Lawrence

    _____
    #ZIP #MOV #TopLevelDomain #TLD #Domain #DNS #UiDesign #WebDesign #WebDevelopment #WebDev #Frontend #URL #Link #FileName #Collisions

  5. Troubleshooting files as a favor for a great cause (#Ethiopian project). Would a messy like Port_(85_of_89).jpg cause errors like this: "Referenced resource "OEBPS/image/Port_(85_of_89).jpg" is not declared in the OPF manifest." 🇪🇹 📚

  6. So, how can I write tests for each input file?

    Something like:

    ```
    // pseudocode!
    for filename in filenames {
    #[test]
    pub fn parse_##filename## {
    parse(filename);
    }
    }
    ```

    Hmm.

  7. When I edit a file in Emacs, it creates a `.#filename` which bothers me right now.

    I have put `(setq remote-file-name-inhibit-locks nil)` and `(setq auto-save-default nil)` in my conf but the annoying file is still here.

    Anyone has a solution for me ?

    #gnu #emacs

  8. @alexandra I mean sure, why not. Now that I think about it, Emacs actually does something similar.

    When you have modified a file, it creates a symlink named .#filename which points to the machine and pid that has the file open:

    $ ls -la
    total 40
    drwxr-xr-x. 2 elias elias 4096 4 okt 12.33 ./
    drwxr-xr-x. 3 elias elias 4096 1 okt 20.36 ../
    -rw-r--r--. 1 elias elias 19947 2 okt 18.27 matrix.fasl
    lrwxrwxrwx. 1 elias elias 29 4 okt 12.33 .#matrix.lisp -> '[email protected]:1633316421'
    -rw-r--r--. 1 elias elias 4078 4 okt 12.32 matrix.lisp
    -rw-r--r--. 1 elias elias 4078 2 okt 18.27 matrix.lisp~
    -rw-r--r--. 1 elias elias 105 29 sep 23.43 package.lisp