From: Carsten Dominik <carsten.dominik@gmail.com>
To: Andrew Hyatt <andrew_hyatt@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Invalid face issues
Date: Thu, 8 Nov 2007 10:31:19 +0100 [thread overview]
Message-ID: <08FC910A-81C7-4309-AA09-D96BBC59165A@gmail.com> (raw)
In-Reply-To: <c8389b600711071234g40c01ef8j5e92b0365df451ed@mail.gmail.com>
On 7Nov2007, at 9:34 PM, Andrew Hyatt wrote:
> I'm not an expert in this, but maybe the issue is that make-glyph
> code is supposed to take a char, and "..." is not a char.
Well, the code takes one character at a time. mapcar on a string
maps the characters. So I turn each character into a glob and put
them all into a vector - if I understand the Emacs Lisp manual
correctly, this is the expected format.....
Lets see, maybe more people will hit this problem and we can collect
more info.
- Carsten
>
> On 11/7/07, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On 6Nov2007, at 8:38 PM, Andrew Hyatt wrote:
>
> > I just spend a good half hour tracking this down. It looks like
> > this, in org-mode is killing me. It look wrong to me, but I'm not
> > an expert:
> >
> > (set-display-table-slot
> > org-display-table 4
> > (vconcat (mapcar
> > (lambda (c) (make-glyph-code c (and (not (stringp org-
> > ellipsis))
> > org-ellipsis)))
> > (if (stringp org-ellipsis) org-ellipsis "..."))))
> >
> > Why are we making a glyph-code out of an ellipsis? We end up with
> > a strange-looking display-table.
>
> This is how I understand this need to be done. Am I not correct?
>
> Anyway, I will revert to the default nil for org-ellipsis and leave
> it to users to
> customize it.
>
> - Carsten
>
> >
> > On 11/6/07, Andrew Hyatt <andrew_hyatt@yahoo.com > wrote: I seem to
> > have an issue where I will be using emacs for a while, and
> > eventually something happens which will corrupt all org buffers,
> > and make them unviewable (the buffer refuses to display, but
> > otherwise does not affect the rest of my emacs session). The error
> > I get is "line-move-partial: Invalid face". I can switch to text-
> > mode and see it normally.
> >
> >
> > I'm using emacs version 23.0.0.1. I'm using org-mode version
> > 5.13a. This seemed to coincide to my upgrade from org-mode version
> > 4 to 5.13a. This happens on both terminal and x-windows versions
> > of emacs.
> >
> >
> > Has anyone experienced this issue before? Any ideas on how to
> > solve it?
> >
> >
> > _______________________________________________
> > Emacs-orgmode mailing list
> > Remember: use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
next prev parent reply other threads:[~2007-11-08 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 16:32 Invalid face issues Andrew Hyatt
2007-11-06 19:38 ` Andrew Hyatt
2007-11-07 8:43 ` Carsten Dominik
2007-11-07 20:34 ` Andrew Hyatt
2007-11-08 9:31 ` Carsten Dominik [this message]
2007-11-08 4:06 ` Alain Picard
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=08FC910A-81C7-4309-AA09-D96BBC59165A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=andrew_hyatt@yahoo.com \
--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).