diff options
| author | Marc André Tanner <mat@brain-dump.org> | 2015-07-17 14:38:36 +0200 |
|---|---|---|
| committer | Marc André Tanner <mat@brain-dump.org> | 2015-07-19 14:12:43 +0200 |
| commit | 0fa9885cda0778467ca5737ac888ece5ef371b3d (patch) | |
| tree | fd3ab531ec8ab1e60b9ee9a782c2c38120202d7b /text.h | |
| parent | 8129933ca51caf788e0cd7c5fdbcb43fdc64601d (diff) | |
| download | vis-0fa9885cda0778467ca5737ac888ece5ef371b3d.tar.gz vis-0fa9885cda0778467ca5737ac888ece5ef371b3d.tar.xz | |
vis: handle file truncation more gracefully
If we use the file / virtual memory system as cache (using mmap(2))
and another process truncates the file we are editing, we have a
problem. All we can do is catch the resulting SIGBUS, close the
corresponding window and print a warning message.
To test this use:
$ dd if=/dev/zero of=TEST bs=8M count=1
$ vis TEST
:! echo TRUNCATE > TEST
Diffstat (limited to 'text.h')
| -rw-r--r-- | text.h | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -108,6 +108,9 @@ size_t text_history_get(Text*, size_t index); size_t text_size(Text*); /* query whether the text contains any unsaved modifications */ bool text_modified(Text*); +/* query whether `addr` is part of a memory mapped region associated with + * this text instance */ +bool text_sigbus(Text*, const char *addr); /* which type of new lines does the text use? */ enum TextNewLine { |
