posix: always seek to EOF when opening a file in append mode Python 3 already does this, so skip it there. Consider the program: #include <stdio.h> int main() { FILE *f = fopen("narf", "w"); fprintf(f, "narf\n"); fclose(f); f = fopen("narf", "a"); printf("%ld\n", ftell(f)); fprintf(f, "troz\n"); printf("%ld\n", ftell(f)); return 0; } on macOS, FreeBSD, and Linux with glibc, this program prints 5 10 but on musl libc (Alpine Linux and probably others) this prints 0 10 By my reading of https://pubs.opengroup.org/onlinepubs/009695399/functions/fopen.html this is technically correct, specifically: > Opening a file with append mode (a as the first character in the > mode argument) shall cause all subsequent writes to the file to be > forced to the then current end-of-file, regardless of intervening > calls to fseek(). in other words, the file position doesn't really matter in append-mode files, and we can't depend on it being at all meaningful unless we perform a seek() before tell() after open(..., 'a'). Experimentally after a .write() we can do a .tell() and it'll always be reasonable, but I'm unclear from reading the specification if that's a smart thing to rely on. This matches what we do on Windows and what Python 3 does for free, so let's just be consistent. Thanks to Yuya for the idea.

     1

  $ rm -rf a

     2

  $ hg init a

     3

  $ cd a

     4

  $ echo a > a

     5

  $ hg ci -Am0

     6

  adding a

     7

  $ hg tag t1 # 1

     8

  $ hg tag --remove t1 # 2

     9

    10

  $ hg co 1

    11

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    12

  $ hg tag -f -r0 t1

    13

  $ hg tags

    14

  tip                                3:a49829c4fc11

    15

  t1                                 0:f7b1eb17ad24

    16

    17

  $ cd ..