3 Commands like @code{ess-display-help-on-object} and list completion
4 cannot be used while the user is entering a multi-line command. The
5 only real fix in this situation is to use another ESS process.
8 The @code{ess-eval-} commands can leave point in the ESS process
9 buffer in the wrong place when point is at the same position as the last
10 process output. This proves difficult to fix, in general, as we need to
11 consider all @emph{windows} with @code{window-point} at the right place.
14 It's possible to clear the modification flag (say, by saving the buffer)
15 with the edit buffer not having been loaded into S.
18 Backup files can sometimes be left behind, even when
19 @code{ess-keep-dump-files} is @code{nil}.
22 Passing an incomplete @Sl{} expression to @code{ess-execute} causes ESS
26 The function-based commands don't always work as expected on functions
27 whose body is not a parenthesized or compound expression, and don't even
28 recognize anonymous functions (i.e. functions not assigned to any
32 Multi-line commands could be handled better by the command history