hasufell/hsfm
1
1
Fork 0
Code Issues 33 Pull Requests Releases Wiki Activity

Minor addition in HACKING.md

Browse Source
This commit is contained in:
hasufell 2016-04-21 02:50:10 +02:00
parent 8348f34a4a
commit 44fc047223
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hacking/HACKING.md
View File

@ -97,7 +97,7 @@ The only problem with this approach is that we are examining a file at point
the call stack at point `b` in time, when the file information in memory the call stack at point `b` in time, when the file information in memory
could already be out of date. There are two approaches to make this less could already be out of date. There are two approaches to make this less
sucky: sucky:
* use the hinotify library on GUI level to refresh the view whenever the contents of a directory changes * use the hinotify library on GUI level to refresh the view (and the File representation in memory) whenever the contents of a directory changes
* when we stuff something into the copy buffer, it is not saved as type `File a`, but as `Path Abs`... when the operation is finalized via `runFileOp`, then the file at the given path is read and the copy/move/whatnot function carried out immediately * when we stuff something into the copy buffer, it is not saved as type `File a`, but as `Path Abs`... when the operation is finalized via `runFileOp`, then the file at the given path is read and the copy/move/whatnot function carried out immediately
This means we should only interact with the `HSFM.FileSystem.FileOperation` This means we should only interact with the `HSFM.FileSystem.FileOperation`