Timeline for What's the point of `save-excursion` twice in `copy-to-buffer`?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2019 at 9:06 | comment | added | Tobias |
The paragraph where the OP speaks about with-current-buffer is wrong. But I think that that is not really the point of the question. The actual point is that save-excursion does not really make sense in the original implementation.
|
|
| Feb 22, 2019 at 6:25 | comment | added | nalzok |
But save-excursion is evaluated within with-current-buffer, where the "current buffer" being saved (and to be restored later) by save-excursion is the buffer to which I am copying. This doesn't seem to be right, because after executing copy-to-buffer, I remain in the old buffer.
|
|
| Feb 22, 2019 at 6:18 | history | answered | Drew | CC BY-SA 4.0 |