From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: Re: eval: Invalid read syntax: "#"Error during redisplay: (void-function -mode) Date: Sat, 11 Dec 2010 12:14:01 -1000 Message-ID: References: <26374.1292004951@gamaville.dokosmarshall.org> <4A9A4769-88C0-4FB3-8D94-17ED3C2DAC81@tsdye.com> <80fwu4f43a.fsf@missioncriticalit.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=36801 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PRXhm-0001fz-6R for emacs-orgmode@gnu.org; Sat, 11 Dec 2010 17:14:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PRXhk-0001Mh-VZ for emacs-orgmode@gnu.org; Sat, 11 Dec 2010 17:14:14 -0500 Received: from oproxy2-pub.bluehost.com ([67.222.39.60]:58047) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1PRXhk-0001KM-Ls for emacs-orgmode@gnu.org; Sat, 11 Dec 2010 17:14:12 -0500 In-Reply-To: <80fwu4f43a.fsf@missioncriticalit.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?ISO-8859-1?Q?S=E9bastien_Vauban?= Cc: emacs-orgmode@gnu.org Aloha Seb, Thanks for looking into this. I pulled as you suggested and now get =20 consistent version strings. I'm pleased that we share a solution to =20 that inconsistency. Thanks! The other problem persists. I put the example in its own buffer and =20 was able to export the entire buffer without problem. Are you able to export a subtree? I get an error if I try to export =20 just the subtree. The problem appears to be related to exporting results. If I =20 have :exports code, all is well. With :exports results or :exports =20 both, the error pops up. Also, I followed your lead and switched off org-src-fontify-natively =20 and org-src-tabify-natively, but neither of these made the error go =20 away. All the best, Tom On Dec 11, 2010, at 10:26 AM, S=E9bastien Vauban wrote: > Hi Thomas, Nick and others, > > "Thomas S. Dye" wrote: >> On Dec 10, 2010, at 8:15 AM, Nick Dokos wrote: >>> Thomas S. Dye wrote: >> So, Seb and I have two things that others can't reproduce: the =20 >> error in the >> OP, and the version string for the latest Org-mode. > > Let's say it's an honor to share things with you ;-) > >>>> I'm using Org-mode version 7.3 (release_7.4.2.g32f816.dirty) > > First, regarding the string problem, as just reported, that has been =20= > fixed. > > Org-mode version 7.4 (release_7.4.6.g561c0) > >>>> I get subject error when exporting this subtree to LaTeX: >>>> >>>> * Export problem >>>> >>>> #+begin_src emacs-lisp :results wrap :exports both >>>> "code block results" >>>> #+end_src >>>> >>>> #+begin_src emacs-lisp :var lst=3Da-list :results list >>>> (reverse lst) >>>> #+end_src >>>> >>>> The error goes away and LaTeX export succeeds if I get rid of =20 >>>> the :exports >>>> header argument in the first source block, or get rid of the =20 >>>> second code >>>> block. >>> >>> This sounds suspiciously like something that Seb ran into a few =20 >>> weeks ago: >>> >>> http://thread.gmane.org/gmane.emacs.orgmode/33922 >>> >>> but I'm not sure how that was resolved. > > I cannot really say it has been resolved. It simply disappeared =20 > after I came > back to a more standard version. I had applied a couple of patches =20 > from Eric > (Org RESULT block) and Dan (fontification minibug), and just git =20 > pulled to > come back to the master branch. > > After that, and with no native fontification anymore[1], it did not =20= > occur > again. But I don't think it has been solved. Simply it occurs in =20 > particular > contexts. > >>> FWIW, I cannot reproduce it: > > I did export the above both to HTML and PDF with no problem. First =20 > code block > is run, and results exported; second simply exported. > > Sorry. Do you still have the problem with current current current =20 > git? No > sandbox with extra patches? > > Best regards, > Seb > > Footnotes: > > [1] "No native fontification" is still my current standard, among =20 > others > because of the fontification minibug -- not yet applied by Dan =20 > --, and > because I need more visibility of code blocks inside the prose -- =20= > see my > patch, not yet accepted, and hopefully other coming patches to =20 > add new > faces to the Babel lines). > > --=20 > S=E9bastien Vauban > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode