emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Richard G Riley <rileyrgdev@googlemail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Problems publishing css files
Date: Wed, 06 Aug 2008 23:50:55 -0400	[thread overview]
Message-ID: <87skth32lc.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: bqhca0criu.fsf@richardriley.net

Richard G Riley <rileyrgdev@googlemail.com> writes:

> I can org-publish both web-org and web-images with no problem. However
> when I try to publish web-css I get:
>
> ,----
> | Debugger entered--Lisp error: (error "Wrong type argument: arrayp, nil")
> |   signal(error ("Wrong type argument: arrayp, nil"))
> |   error("%s" "Wrong type argument: arrayp, nil")
> |   byte-code("Â\b!ˆÃÄÅ	!\"‡" [orig-buff act-on-choice icicle-try-switch-buffer error "%s" error-message-string] 4)
> |   icicle-execute-extended-command()
> |   call-interactively(icicle-execute-extended-command)
> `----
>
> I can org-publish-current-file with no problem.
>
> (I have tried it without icicles loaded too). It is only css files (in
> this instance) causing this. Any suggestions on how to debug this? What
> could it be? I have tried without nxhtml loaded too and have ensured the
> only css mode I have in the one that comes with emacs 22.
>
> org : 6.06b
> emacs : 22.2.1
>
> Can anyone confirm (using emacs 22) that they can publish css files
> without a problem?

I'm in the process of finally setting up org-publish for some of my
reference information.  I'm converting another system to org and I get a
similar error (but not identical) due to some of my org files that are
not the correct structure.  I was lazy and just renamed my original
*.txt files to *.org and I haven't completed editing them to convert
them to valid org files.  When I try to export with the wrong format I
get:

,----
| Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
|   1-(nil)
|   (max (point-min) (1- (previous-single-property-change ... ...)))
|   (get-text-property (max (point-min) (1- ...)) (quote target))
|   (or (get-text-property (point) (quote target)) (get-text-property (max ... ...) (quote target)))
|   (progn (or (get-text-property ... ...) (get-text-property ... ...)))
|   (if (and found (or ... ...)) (progn (or ... ...)))
|   ...
`----

Maybe your problem is some other css file that the web-css project is
picking up?

If I load a problem file then org-publish-current-file fails with the
above error.

I may be completely off-base here... but it's something else to look at.

-Bernt

      parent reply	other threads:[~2008-08-07  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 23:03 Problems publishing css files Richard G Riley
2008-08-05  9:28 ` Dan Davison
2008-08-05 12:45   ` Richard G Riley
2008-08-07  3:50 ` Bernt Hansen [this message]

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=87skth32lc.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.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).