On 11/18/2013 3:53 PM, SDS wrote:
Update on the session that produced this error earlier:
On 11/18/2013 3:14 PM, SDS wrote:
More information about Lisp errors. I got a different Lisp error while
leaving emacs-w32 -Q with TRAMP in the background. Output from the Lisp
Debugger is shown below:
On 11/17/2013 7:43 PM, SDS wrote:
Emacs-w32 aborts about once/twice a day when using SSH with TRAMP. I
rarely use Emacs without TRAMP, so I'm not sure whether this issue is
really related to TRAMP. The abort doesn't appear to be caused by
direct user input, as I've seen background sessions that
Ken Brown writes:
Can you do some experimentation to try to narrow this down? For example:
* Is it related to Tramp or not?
I don't think so, I get those crashes without Tramp in the picture and
sometimes with an Emacs that simply has a single file open and then left
alone.
FWIW, besides
On 11/18/2013 9:21 AM, Ken Brown wrote:
Can you do some experimentation to try to narrow this down? For example:
* Is it related to Tramp or not?
* Does the abort still occur if you start emacs with emacs -Q?
* Is the problem specific to emacs-w32 or does it happen with emacs-nox and
More information about Lisp errors. I got a different Lisp error while
leaving emacs-w32 -Q with TRAMP in the background. Output from the Lisp
Debugger is shown below:
Debugger entered--Lisp error: (error Lisp nesting exceeds
`max-lisp-eval-depth')
seconds-to-time(0.5)
Update on the session that produced this error earlier:
On 11/18/2013 3:14 PM, SDS wrote:
More information about Lisp errors. I got a different Lisp error while
leaving emacs-w32 -Q with TRAMP in the background. Output from the Lisp
Debugger is shown below:
Debugger entered--Lisp error:
Ran another session of emacs-w32 -Q with TRAMP. Opened a Dired buffer
and a file on the remote. The previous session with these conditions did
this:
On 11/18/2013 3:53 PM, SDS wrote:
On 11/18/2013 3:14 PM, SDS wrote:
More information about Lisp errors. I got a different Lisp error while
7 matches
Mail list logo
