Menu

#296 Add flag to prevent DEADJOE from being created

v3.8
closed-fixed
None
v3.7
5
2019-02-09
2014-11-11
No

Discussion

  • Egmont Koblinger

    +1 here

    I don't quite the purpose of DEADJOE - I never find actual useful information there (that is: unsaved contents of the file I was editing). It's just metadata about which files I was editing, hardly useful after a crash.

     
  • John J. Jordan

    John J. Jordan - 2015-02-21

    It ought to save out the full file if it was modified. The relevant code is in ttsig() in b.c:

    for (b = bufs.link.next; b != &bufs; b = b->link.next)
        if (b->changed) {
            if (b->name)
                fprintf(ttsig_f, "\n*** File \'%s\'\n", b->name);
            else
                fprintf(ttsig_f, "\n*** File \'(Unnamed)\'\n");
            fflush(ttsig_f);
            bsavefd(b->bof, fileno(ttsig_f), b->eof->byte);
        }
    

    If it isn't saving out a modified file, then that's a bug.

     
  • Egmont Koblinger

    I don't know why I had the impression that it never put anything useful in that file. Works for me now.

     
  • John J. Jordan

    John J. Jordan - 2015-03-14

    Patch

     
  • John J. Jordan

    John J. Jordan - 2015-03-24
    • status: open --> closed-fixed
    • assigned_to: Joe Allen
    • Applies To: --> v3.7
     
  • John J. Jordan

    John J. Jordan - 2015-03-24

    Fixed in [8a1176]

     

    Related

    Commit: [8a1176]

  • Gerrit Griebel

    Gerrit Griebel - 2019-02-09

    I like DEADJOE files, but only for normal buffers, not for minibuffers containing only filenames and text of incremental searches. Should I reopen this one or file a new issue or is there an existing option to avoid such entries in DEADJOE files?

     

Log in to post a comment.