emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, zwz <zhangweize@gmail.com>
Subject: Re: 6.29c export latex bug?
Date: Mon, 10 Aug 2009 23:26:01 -0400	[thread overview]
Message-ID: <11010.1249961161@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Mon, 10 Aug 2009 20:21:40 EDT." <15967.1249950100@alphaville.usa.hp.com>

Nick Dokos <nicholas.dokos@hp.com> wrote:


> 31ceed47ffd3070418dd34316fef8869d2434c26 is first bad commit
> commit 31ceed47ffd3070418dd34316fef8869d2434c26
> Author: Carsten Dominik <carsten.dominik@gmail.com>
> Date:   Tue Jun 30 07:24:57 2009 +0200
> 
>     New minor mode org-indent-mode
>     
>     This mode implements outline indentation similar to clean view, but in
>     a dynamic and virtual way, at display time.
> 

I looked over the commit and saw this change to org-table.el:

    ...
    (if (equal (char-before) ?\n)
        ;; This hack is for org-indent, to force redisplay of the
        ;; line prefix of the first line. Apparently the redisplay
        ;; is tied to the newline, which is, I think, a bug.
        ;; To force this redisplay, we remove and re-insert the
        ;; newline, so that the redisplay engine thinks it belongs
        ;; to the changed text.
        (progn
          (backward-delete-char 1)
          (insert "\n")))
    ...

I commented it out and the export of the table worked - but I have no
idea why.

Nick

  reply	other threads:[~2009-08-11  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 21:26 6.29c export latex bug? zwz
2009-08-10 21:53 ` zwz
2009-08-11  0:21 ` Nick Dokos
2009-08-11  3:26   ` Nick Dokos [this message]
2009-08-11  7:47     ` Carsten Dominik
2009-08-11 12:54       ` Nick Dokos

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=11010.1249961161@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=zhangweize@gmail.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).