emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff Horn <jrhorn424@gmail.com>
To: nicholas.dokos@hp.com
Cc: Bernt Hansen <bernt@norang.ca>, Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Re: Need help with org and SSH
Date: Thu, 23 Dec 2010 01:41:02 -0500	[thread overview]
Message-ID: <AANLkTi=JEouHYfLjobuNr77gOcptMZ6otb=YU0LZB6iu@mail.gmail.com> (raw)
In-Reply-To: <15285.1293056289@gamaville.americas.hpqcorp.net>

I'll post a backtrace as soon as I figure out how to get this stuff
out of the Chrome OS shell. I might be able to send mail through gnus,
assuming it isn't affected by this error.

Jeff

On Wed, Dec 22, 2010 at 5:18 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> Jeff Horn <jrhorn424@gmail.com> wrote:
>
>> I enabled debug-on-quit and tried looking at the backtrace while the
>> agenda was hanging. Somewhere along the way, many lines before the
>> error occurs, "~/org" is *correctly* translated as
>> "/Users/jeffreyhorn/Dropbox/org". The error is occurring immediately
>> after org "prepares buffers" (the org files). The last few lines of
>> the backtrace are:
>>
>> org-agenda(nil)
>> call-interactively(org-agenda nil nil)
>>
>
> Actually, the top few lines are probably more informative.
>
>> I'll try moving the agenda file to my home directory and see what happens.
>>
>> (interlude)
>>
>> OK. I created a very simple two line org file with a single todo and
>> placed it in my home directory. Starting a new emacs session and
>> visiting the file is enough to trigger the error. Visiting a buffer of
>> another type (text for instance) *also* produces this error.
>>
>
> Well, that's good - lets org off the hook and probably indicts your
> setup (both .emacs and maybe the structure of your home directory itself).
> Can you post the backtrace for this?
>
> Also try evaluating the following (fix the path of course):
>
>    (file-truename "/path/to/suspect/file")
>
> C-x C-e with the cursor right after the closing paren should do it.
> Post this backtrace as well, assuming you get one.
>
> Nick
>



-- 
Jeffrey Horn
Graduate Lecturer and PhD Student in Economics
George Mason University

(704) 271-4797
jhorn@gmu.edu
jrhorn424@gmail.com

http://www.failuretorefrain.com/jeff/

  reply	other threads:[~2010-12-23  6:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 17:10 Need help with org and SSH Jeff Horn
2010-12-22 17:45 ` Bernt Hansen
2010-12-22 18:28   ` Jeff Horn
2010-12-22 19:00     ` Jeff Horn
2010-12-22 19:59       ` Jeff Horn
2010-12-22 20:32         ` Nick Dokos
2010-12-22 22:07           ` Jeff Horn
2010-12-22 22:18             ` Nick Dokos
2010-12-23  6:41               ` Jeff Horn [this message]
2010-12-23  7:23               ` Jeff Horn
2010-12-22 17:49 ` Dan Davison
2010-12-22 18:18   ` Jeff Horn
2010-12-23  1:06     ` Dan Davison
2010-12-23  6:40       ` Jeff Horn
2010-12-23  7:36   ` [Accepted] " Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=JEouHYfLjobuNr77gOcptMZ6otb=YU0LZB6iu@mail.gmail.com' \
    --to=jrhorn424@gmail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).