emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Bug in iCalendar export
Date: Wed, 28 May 2008 23:05:51 +0100	[thread overview]
Message-ID: <20080528220551.GJ20846@atlantic.linksys.moosehall> (raw)
In-Reply-To: <87iqwyf8gi.fsf@gmail.com>

On Wed, May 28, 2008 at 11:02:37PM +0200, Paul R wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> You have some faulty site-lisp code provided by debian emacs packages.
> Because it was the Nth bug I had to track down due to the way debian
> handles site-lisp, I just decided to get rid, for good, of debian
> emacs packages, and do everything by hand. So I'm sorry to tell you
> that I can't tell what line is faulty this time. But I can tell, for
> sure, that it lives in debian site-lisp. Good luck.

I'm not sure this bug is specific to Debian - it has been plaguing me
on Fedora... unless there are two separate causes of the same error
message.

To be honest I'm not even convinced it's directly related to orgmode.
In my case it looks related to uniquify, but you (Paul) already said
that you are not using uniquify, which is weird.  I did some digging
into it before but got lost in a maze of twisty function calls, all
alike.  In case anyone's interested, my notes say:

  ** uniquify-managed ends up with a deleted buffer for some reason
  ** instrument `uniquify-rationalize-file-buffer-names'

  reply	other threads:[~2008-05-28 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 20:03 Bug in iCalendar export Nick Dokos
2008-05-28 21:02 ` Paul R
2008-05-28 22:05   ` Adam Spiers [this message]
2008-05-29  9:29     ` Paul R
2008-05-29 17:12       ` Adam Spiers
2008-06-11 23:13   ` Nick Dokos
2008-06-12  7:53     ` Paul R
2008-06-12 14:44       ` Nick Dokos
2008-06-12 10:03     ` Adam Spiers
2008-06-12 15:20       ` Adam Spiers

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=20080528220551.GJ20846@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --cc=emacs-orgmode@gnu.org \
    /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).