Menu ▾ ▴

#156 ghost source files

workingwiki
open
Lee Worden
None
6
2013-05-07
2012-01-13
Lee Worden
No

I have received a report that .mk files that have been removed from a project sometimes reappear in the working directory, causing frustration and confusion, because that can make the project's behaviour really hard to diagnose.

Discussion

  • Lee Worden

    Lee Worden - 2012-01-13

    The remove-source-file operation should always remove from the working directory, regardless of whether it removes from the project and/or wiki pages as well. Maybe it's working right, but subsequently the file reappears because it's present in a preview or background session that gets merged into the directory?

     

  • Lee Worden

    Lee Worden - 2012-01-13

    The original report is at http://sourceforge.net/tracker/?func=detail&aid=3473112&group_id=366300&atid=1527385:

    The ghost Makefile problem. Somebody somehow deletes a .mk file from the
    PD, but it remains in the working directory. These have caused major
    nightmares on at least 3 occasions. The kind of thing that could make
    someone give up on WW, IMO.

     

  • Jonathan Dushoff

    Jonathan Dushoff - 2012-01-14

    I don't know how long ago it last happened, nor how WW was working at that time. And we do have the feature that it tells people what files it's including.

    But I still suggest giving make access to a variable that lists the source files, and constructing a list of included make files from that.

    It's very hard to keep track of all the ways a file could show up in a project directory: examples include ephemeral errors in a make file, or unpacking of zip files.

    People who are constructing make files can be expected to be aware that they are doing something complicated and to be willing to specify that constructed make files be included.

     

  • Lee Worden

    Lee Worden - 2012-03-09

    It should not be possible to repopulate a file from a preview session, by the way, because the preview files don't get merged back in if anything has been done in the persistent directory since the preview directory was created.

     

  • Lee Worden

    Lee Worden - 2012-09-07

    https://sourceforge.net/p/workingwiki/bugs/211/ (rewrite .mk inclusion rule to use $(WW_THIS_PROJECT_SOURCE_FILES)) might help with this.

     

  • Jonathan Dushoff

    Jonathan Dushoff - 2013-04-03

    What's the desired behaviour if I remove a source file during preview operations? I think it should be to remove it from the project and the main project directory after I save.

     

    • Lee Worden

      Lee Worden - 2013-04-03

      Shifting this question to new ticket [#280]

       

      Related

      Bugs: #280

  • Lee Worden

    Lee Worden - 2013-04-03

    Regarding basepars.pl: it's great news if we have a live case that can lead us to the source of this weird behavior.

    I don't know what to try to make it appear after being removed. It would be great if you (or whoever is doing the work in this project) could do some tests to gather information on this file:

    • save or close any existing preview sessions.
    • remove it from the main project directory.
    • open a "list directory contents" page for the main directory, and for any preview session you open
    • after each operation, refresh the directory listing and see if the file has appeared.
    • if it does appear, tell me what you did, and especially what was the last operation.
     

Anonymous
Anonymous

Add attachments
Cancel