comparison src/fileio.c @ 3638:305157cf3ebb

[xemacs-hg @ 2006-10-27 19:07:32 by aidan] Deal with buffer-reversion with non-binary coding better; update fileio.c comment from Ben.
author aidan
date Fri, 27 Oct 2006 19:07:47 +0000
parents 6c7605dfcf07
children 3e7493e76dc7
comparison
equal deleted inserted replaced
3637:9ea4f17ba0db 3638:305157cf3ebb
2946 beginning to that point, but I really don't think it's worth it. If 2946 beginning to that point, but I really don't think it's worth it. If
2947 we implemented the FSF "brute-force" method, we would have to put a 2947 we implemented the FSF "brute-force" method, we would have to put a
2948 reasonable maximum file size on the files. Is any of this worth it? 2948 reasonable maximum file size on the files. Is any of this worth it?
2949 --ben 2949 --ben
2950 2950
2951
2952 It's probably not worth it, and despite what you might take from the
2953 above, we don't do it currently; that is, for non-"binary" coding
2954 systems, we don't try to implement replace-mode at all. See the
2955 do_speedy_insert variable above. The upside of this is that our API
2956 is consistent and not buggy. -- Aidan Kehoe, Fri Oct 27 21:02:30 CEST
2957 2006
2951 */ 2958 */
2952 2959
2953 if (!NILP (replace)) 2960 if (!NILP (replace))
2954 { 2961 {
2955 if (!do_speedy_insert) 2962 if (!do_speedy_insert)