* Bug?
@ 2002-08-28 17:41 Sharon A Watkins
2002-08-29 1:38 ` Bug? Juanma Barranquero
2002-08-29 4:44 ` Bug? Eli Zaretskii
0 siblings, 2 replies; 44+ messages in thread
From: Sharon A Watkins @ 2002-08-28 17:41 UTC (permalink / raw)
I am running emacs on a WinOS system a getting an annoying error message:
"Creating directory: permission denied, c:\.emacs.d"
I've tried making the directory for emacs as administrator, but WinOS
doesn't
like directories that start with a period. The message itself isn't too
troublesome,
but my system dings each time it comes up, and it comes up continuously.
Also, when I exit emacs, I get a fatal error.
Cheers!
Sharon
Sharon A. Watkins
Hydrologist
U.S. Geological Survey
Water Resources Division
333 West Nye Lane, Room 203
Carson City, NV 89706
Office: (775) 887-7607
Fax: (775) 887-7629
E-Mail: swatkins@usgs.gov
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2002-08-28 17:41 Bug? Sharon A Watkins
@ 2002-08-29 1:38 ` Juanma Barranquero
2002-08-29 4:44 ` Bug? Eli Zaretskii
1 sibling, 0 replies; 44+ messages in thread
From: Juanma Barranquero @ 2002-08-29 1:38 UTC (permalink / raw)
Cc: Bug-gnu-emacs
On Wed, 28 Aug 2002 10:41:40 -0700
"Sharon A Watkins" <swatkins@usgs.gov> wrote:
> "Creating directory: permission denied, c:\.emacs.d"
>
> I've tried making the directory for emacs as administrator, but WinOS
> doesn't like directories that start with a period.
I assume you´re using W95, W98 or Me. Windows Explorer won´t let you
create it, but you can do it from COMMAND.COM (from the Start menu chose
Run, then type COMMAND and press ENTER). You´ll be in COMMAND.COM, then
do:
cd \ (and press ENTER)
md .emacs.d (and ENTER)
exit (and ENTER)
and you´ll have the directory. (BTW, sorry if I´m being very basic here,
I don´t know how familiar you are with Windows and COMMAND.COM).
> but my system dings each time it comes up, and it comes up continuously.
> Also, when I exit emacs, I get a fatal error.
There are ways to make Emacs to not ding on error, if you so desire.
--
Juanma Barranquero <lektu@terra.es>
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2002-08-28 17:41 Bug? Sharon A Watkins
2002-08-29 1:38 ` Bug? Juanma Barranquero
@ 2002-08-29 4:44 ` Eli Zaretskii
1 sibling, 0 replies; 44+ messages in thread
From: Eli Zaretskii @ 2002-08-29 4:44 UTC (permalink / raw)
Cc: Bug-gnu-emacs
On Wed, 28 Aug 2002, Sharon A Watkins wrote:
> I am running emacs on a WinOS system a getting an annoying error message:
>
> "Creating directory: permission denied, c:\.emacs.d"
>
> I've tried making the directory for emacs as administrator, but WinOS
> doesn't
> like directories that start with a period.
That's not true: it's only some Windows applications, notably the
Explorer, prevent you from creating such directories and files. But the
Windows filesystem itself is perfectly happy with names like .emacs.d.
So the problem lies elsewhere. Can you post the output of the command
"dir c:\" typed from a DOS box?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Bug?
@ 2003-09-23 11:07 Mark Espinoza
0 siblings, 0 replies; 44+ messages in thread
From: Mark Espinoza @ 2003-09-23 11:07 UTC (permalink / raw)
[-- Attachment #1: Type: text/html, Size: 1304 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
^ permalink raw reply [flat|nested] 44+ messages in thread
* bug ?
@ 2005-03-07 16:35 fg
0 siblings, 0 replies; 44+ messages in thread
From: fg @ 2005-03-07 16:35 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
hello, emacs don't work.... since few day....
fg@nobody fg $ emacs
Fatal error (6).Abandon
fg@nobody fg $ su
Password:
root@nobody fg # emacs
Fatal error (6).Abandon
root@nobody fg #
<stdin>:76: directive de pré-traitement #emacs invalide
<stdin>:77: directive de pré-traitement #emacs invalide
<stdin>:78: directive de pré-traitement #emacs invalide
<stdin>:79: directive de pré-traitement #emacs invalide
<stdin>:80: directive de pré-traitement #emacs invalide
<stdin>:81: directive de pré-traitement #emacs invalide
<stdin>:82: directive de pré-traitement #emacs invalide
^ permalink raw reply [flat|nested] 44+ messages in thread
* bug?
@ 2010-05-12 12:50 J. David Boyd
2010-05-12 13:35 ` bug? Bernt Hansen
0 siblings, 1 reply; 44+ messages in thread
From: J. David Boyd @ 2010-05-12 12:50 UTC (permalink / raw)
To: emacs-orgmode
When I type org-version, I get a shell-command window opened, and this:
error: refs/heads/master does not point to a valid object!
error: refs/remotes/origin/HEAD does not point to a valid object!
error: refs/remotes/origin/add-recursion-to-org-publish does not point to a valid object!
error: refs/remotes/origin/beamer does not point to a valid object!
error: refs/remotes/origin/emacs23 does not point to a valid object!
error: refs/remotes/origin/experimental does not point to a valid object!
error: refs/remotes/origin/experimental-code-for-the-new-export-engine does not point to a valid object!
error: refs/remotes/origin/master does not point to a valid object!
error: refs/remotes/origin/mobile-support does not point to a valid object!
error: refs/remotes/origin/org-plot-doc does not point to a valid object!
error: refs/remotes/origin/support-for-mobile-sync does not point to a valid object!
error: refs/tags/5.23a does not point to a valid object!
error: refs/tags/rel519 does not point to a valid object!
error: refs/tags/release_ does not point to a valid object!
error: refs/tags/release_4.12a does not point to a valid object!
error: refs/tags/release_4.13 does not point to a valid object!
error: refs/tags/release_4.19a does not point to a valid object!
error: refs/tags/release_4.19b does not point to a valid object!
error: refs/tags/release_4.20 does not point to a valid object!
error: refs/tags/release_4.21 does not point to a valid object!
error: refs/tags/release_4.22 does not point to a valid object!
error: refs/tags/release_4.23 does not point to a valid object!
error: refs/tags/release_4.24 does not point to a valid object!
error: refs/tags/release_4.26 does not point to a valid object!
error: refs/tags/release_4.27 does not point to a valid object!
error: refs/tags/release_4.28 does not point to a valid object!
error: refs/tags/release_4.29 does not point to a valid object!
error: refs/tags/release_4.30 does not point to a valid object!
error: refs/tags/release_4.33 does not point to a valid object!
error: refs/tags/release_4.34 does not point to a valid object!
error: refs/tags/release_4.36 does not point to a valid object!
error: refs/tags/release_4.37 does not point to a valid object!
error: refs/tags/release_4.40 does not point to a valid object!
error: refs/tags/release_4.41 does not point to a valid object!
error: refs/tags/release_4.42 does not point to a valid object!
error: refs/tags/release_4.43 does not point to a valid object!
error: refs/tags/release_4.44 does not point to a valid object!
error: refs/tags/release_4.45 does not point to a valid object!
error: refs/tags/release_4.46 does not point to a valid object!
error: refs/tags/release_4.48 does not point to a valid object!
error: refs/tags/release_4.50 does not point to a valid object!
error: refs/tags/release_4.51 does not point to a valid object!
error: refs/tags/release_4.52 does not point to a valid object!
error: refs/tags/release_4.53 does not point to a valid object!
error: refs/tags/release_4.54 does not point to a valid object!
error: refs/tags/release_4.55 does not point to a valid object!
error: refs/tags/release_4.56 does not point to a valid object!
error: refs/tags/release_4.57 does not point to a valid object!
error: refs/tags/release_4.58 does not point to a valid object!
error: refs/tags/release_4.59 does not point to a valid object!
error: refs/tags/release_4.60 does not point to a valid object!
error: refs/tags/release_4.61 does not point to a valid object!
error: refs/tags/release_4.62 does not point to a valid object!
error: refs/tags/release_4.64 does not point to a valid object!
error: refs/tags/release_4.65 does not point to a valid object!
error: refs/tags/release_4.66 does not point to a valid object!
error: refs/tags/release_4.67 does not point to a valid object!
error: refs/tags/release_4.68 does not point to a valid object!
error: refs/tags/release_4.69 does not point to a valid object!
error: refs/tags/release_4.70 does not point to a valid object!
error: refs/tags/release_4.71 does not point to a valid object!
error: refs/tags/release_4.72 does not point to a valid object!
error: refs/tags/release_4.74 does not point to a valid object!
error: refs/tags/release_4.75 does not point to a valid object!
error: refs/tags/release_4.76 does not point to a valid object!
error: refs/tags/release_4.77 does not point to a valid object!
error: refs/tags/release_4.78 does not point to a valid object!
error: refs/tags/release_4.79 does not point to a valid object!
error: refs/tags/release_5.01 does not point to a valid object!
error: refs/tags/release_5.01b does not point to a valid object!
error: refs/tags/release_5.02 does not point to a valid object!
error: refs/tags/release_5.03 does not point to a valid object!
error: refs/tags/release_5.03n does not point to a valid object!
error: refs/tags/release_5.04 does not point to a valid object!
error: refs/tags/release_5.05 does not point to a valid object!
error: refs/tags/release_5.06 does not point to a valid object!
error: refs/tags/release_5.06b does not point to a valid object!
error: refs/tags/release_5.06c does not point to a valid object!
error: refs/tags/release_5.06d does not point to a valid object!
error: refs/tags/release_5.06e does not point to a valid object!
error: refs/tags/release_5.07 does not point to a valid object!
error: refs/tags/release_5.07a does not point to a valid object!
error: refs/tags/release_5.10a does not point to a valid object!
error: refs/tags/release_5.10b does not point to a valid object!
error: refs/tags/release_5.11 does not point to a valid object!
error: refs/tags/release_5.11b does not point to a valid object!
error: refs/tags/release_5.12 does not point to a valid object!
error: refs/tags/release_5.12b does not point to a valid object!
error: refs/tags/release_5.12c does not point to a valid object!
error: refs/tags/release_5.13 does not point to a valid object!
error: refs/tags/release_5.13a does not point to a valid object!
error: refs/tags/release_5.13c does not point to a valid object!
error: refs/tags/release_5.13d does not point to a valid object!
error: refs/tags/release_5.13e does not point to a valid object!
error: refs/tags/release_5.13g does not point to a valid object!
error: refs/tags/release_5.13h does not point to a valid object!
error: refs/tags/release_5.13i does not point to a valid object!
error: refs/tags/release_5.14 does not point to a valid object!
error: refs/tags/release_5.15 does not point to a valid object!
error: refs/tags/release_5.15a does not point to a valid object!
error: refs/tags/release_5.16 does not point to a valid object!
error: refs/tags/release_5.16a does not point to a valid object!
error: refs/tags/release_5.16b does not point to a valid object!
error: refs/tags/release_5.17 does not point to a valid object!
error: refs/tags/release_5.17a does not point to a valid object!
error: refs/tags/release_5.18 does not point to a valid object!
error: refs/tags/release_5.18a does not point to a valid object!
error: refs/tags/release_5.19 does not point to a valid object!
error: refs/tags/release_5.19a does not point to a valid object!
error: refs/tags/release_5.20 does not point to a valid object!
error: refs/tags/release_5.21 does not point to a valid object!
error: refs/tags/release_5.22 does not point to a valid object!
error: refs/tags/release_5.22a does not point to a valid object!
error: refs/tags/release_5.23a does not point to a valid object!
error: refs/tags/release_6.01 does not point to a valid object!
error: refs/tags/release_6.01a does not point to a valid object!
error: refs/tags/release_6.01b does not point to a valid object!
error: refs/tags/release_6.01c does not point to a valid object!
error: refs/tags/release_6.02 does not point to a valid object!
error: refs/tags/release_6.02a does not point to a valid object!
error: refs/tags/release_6.02b does not point to a valid object!
error: refs/tags/release_6.03 does not point to a valid object!
error: refs/tags/release_6.04 does not point to a valid object!
error: refs/tags/release_6.04a does not point to a valid object!
error: refs/tags/release_6.04b does not point to a valid object!
error: refs/tags/release_6.04c does not point to a valid object!
error: refs/tags/release_6.05 does not point to a valid object!
error: refs/tags/release_6.05a does not point to a valid object!
error: refs/tags/release_6.05b does not point to a valid object!
error: refs/tags/release_6.06 does not point to a valid object!
error: refs/tags/release_6.06a does not point to a valid object!
error: refs/tags/release_6.06b does not point to a valid object!
error: refs/tags/release_6.07 does not point to a valid object!
error: refs/tags/release_6.07a does not point to a valid object!
error: refs/tags/release_6.07b does not point to a valid object!
error: refs/tags/release_6.08 does not point to a valid object!
error: refs/tags/release_6.08a does not point to a valid object!
error: refs/tags/release_6.08c does not point to a valid object!
error: refs/tags/release_6.09 does not point to a valid object!
error: refs/tags/release_6.09a does not point to a valid object!
error: refs/tags/release_6.10 does not point to a valid object!
error: refs/tags/release_6.10a does not point to a valid object!
error: refs/tags/release_6.10b does not point to a valid object!
error: refs/tags/release_6.10c does not point to a valid object!
error: refs/tags/release_6.11 does not point to a valid object!
error: refs/tags/release_6.11a does not point to a valid object!
error: refs/tags/release_6.11b does not point to a valid object!
error: refs/tags/release_6.11c does not point to a valid object!
error: refs/tags/release_6.12 does not point to a valid object!
error: refs/tags/release_6.12a does not point to a valid object!
error: refs/tags/release_6.12b does not point to a valid object!
error: refs/tags/release_6.13 does not point to a valid object!
error: refs/tags/release_6.13a does not point to a valid object!
error: refs/tags/release_6.14 does not point to a valid object!
error: refs/tags/release_6.15 does not point to a valid object!
error: refs/tags/release_6.15a does not point to a valid object!
error: refs/tags/release_6.15b does not point to a valid object!
error: refs/tags/release_6.15c does not point to a valid object!
error: refs/tags/release_6.15d does not point to a valid object!
error: refs/tags/release_6.15f does not point to a valid object!
error: refs/tags/release_6.16 does not point to a valid object!
error: refs/tags/release_6.16a does not point to a valid object!
error: refs/tags/release_6.16b does not point to a valid object!
error: refs/tags/release_6.16c does not point to a valid object!
error: refs/tags/release_6.17 does not point to a valid object!
error: refs/tags/release_6.17a does not point to a valid object!
error: refs/tags/release_6.17b does not point to a valid object!
error: refs/tags/release_6.17c does not point to a valid object!
error: refs/tags/release_6.18 does not point to a valid object!
error: refs/tags/release_6.18a does not point to a valid object!
error: refs/tags/release_6.18b does not point to a valid object!
error: refs/tags/release_6.18c does not point to a valid object!
error: refs/tags/release_6.19 does not point to a valid object!
error: refs/tags/release_6.19a does not point to a valid object!
error: refs/tags/release_6.19b does not point to a valid object!
error: refs/tags/release_6.19c does not point to a valid object!
error: refs/tags/release_6.19d does not point to a valid object!
error: refs/tags/release_6.19e does not point to a valid object!
error: refs/tags/release_6.20 does not point to a valid object!
error: refs/tags/release_6.20a does not point to a valid object!
error: refs/tags/release_6.20b does not point to a valid object!
error: refs/tags/release_6.20c does not point to a valid object!
error: refs/tags/release_6.20d does not point to a valid object!
error: refs/tags/release_6.20e does not point to a valid object!
error: refs/tags/release_6.20f does not point to a valid object!
error: refs/tags/release_6.20g does not point to a valid object!
error: refs/tags/release_6.20h does not point to a valid object!
error: refs/tags/release_6.20i does not point to a valid object!
error: refs/tags/release_6.21 does not point to a valid object!
error: refs/tags/release_6.21a does not point to a valid object!
error: refs/tags/release_6.21b does not point to a valid object!
error: refs/tags/release_6.22 does not point to a valid object!
error: refs/tags/release_6.22a does not point to a valid object!
error: refs/tags/release_6.22b does not point to a valid object!
error: refs/tags/release_6.23 does not point to a valid object!
error: refs/tags/release_6.23a does not point to a valid object!
error: refs/tags/release_6.23b does not point to a valid object!
error: refs/tags/release_6.24 does not point to a valid object!
error: refs/tags/release_6.24a does not point to a valid object!
error: refs/tags/release_6.24b does not point to a valid object!
error: refs/tags/release_6.24c does not point to a valid object!
error: refs/tags/release_6.25 does not point to a valid object!
error: refs/tags/release_6.25a does not point to a valid object!
error: refs/tags/release_6.25b does not point to a valid object!
error: refs/tags/release_6.25c does not point to a valid object!
error: refs/tags/release_6.25d does not point to a valid object!
error: refs/tags/release_6.25e does not point to a valid object!
error: refs/tags/release_6.25f does not point to a valid object!
error: refs/tags/release_6.26 does not point to a valid object!
error: refs/tags/release_6.26a does not point to a valid object!
error: refs/tags/release_6.26b does not point to a valid object!
error: refs/tags/release_6.26c does not point to a valid object!
error: refs/tags/release_6.26d does not point to a valid object!
error: refs/tags/release_6.27 does not point to a valid object!
error: refs/tags/release_6.27a does not point to a valid object!
error: refs/tags/release_6.28 does not point to a valid object!
error: refs/tags/release_6.28a does not point to a valid object!
error: refs/tags/release_6.28b does not point to a valid object!
error: refs/tags/release_6.28c does not point to a valid object!
error: refs/tags/release_6.28d does not point to a valid object!
error: refs/tags/release_6.28e does not point to a valid object!
error: refs/tags/release_6.29 does not point to a valid object!
error: refs/tags/release_6.29a does not point to a valid object!
error: refs/tags/release_6.29b does not point to a valid object!
error: refs/tags/release_6.29c does not point to a valid object!
error: refs/tags/release_6.30 does not point to a valid object!
error: refs/tags/release_6.30a does not point to a valid object!
error: refs/tags/release_6.30b does not point to a valid object!
error: refs/tags/release_6.30c does not point to a valid object!
error: refs/tags/release_6.30d does not point to a valid object!
error: refs/tags/release_6.30e does not point to a valid object!
error: refs/tags/release_6.31 does not point to a valid object!
error: refs/tags/release_6.32 does not point to a valid object!
error: refs/tags/release_6.32a does not point to a valid object!
error: refs/tags/release_6.32b does not point to a valid object!
error: refs/tags/release_6.33 does not point to a valid object!
error: refs/tags/release_6.33a does not point to a valid object!
error: refs/tags/release_6.33b does not point to a valid object!
error: refs/tags/release_6.33c does not point to a valid object!
error: refs/tags/release_6.33d does not point to a valid object!
error: refs/tags/release_6.33e does not point to a valid object!
error: refs/tags/release_6.33f does not point to a valid object!
error: refs/tags/release_6.34 does not point to a valid object!
error: refs/tags/release_6.34a does not point to a valid object!
error: refs/tags/release_6.34b does not point to a valid object!
error: refs/tags/release_6.34c does not point to a valid object!
error: refs/tags/test_5.21_tagging does not point to a valid object!
fatal: No names found, cannot describe anything.
I just updated to emacs 23.2, and I"m using the latest org, downloaded
with
wget http://orgmode.org/org-latest.tar.gz
Anyone else seen this? Is this an ORG bug, or an EMACS bug?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: bug?
2010-05-12 12:50 bug? J. David Boyd
@ 2010-05-12 13:35 ` Bernt Hansen
2010-05-12 14:32 ` bug? J. David Boyd
0 siblings, 1 reply; 44+ messages in thread
From: Bernt Hansen @ 2010-05-12 13:35 UTC (permalink / raw)
To: J. David Boyd; +Cc: emacs-orgmode
Hi David,
It's org-mode and not Emacs.
This is output from 'git describe' trying to identify the git version
you are running. Did you unpack that archive in a directory with a git
archive (containing a .git subdirectory?)
Does
(locate-library "org")
return some other location than where you unpacked this archive and does
it have a .git subdirectory?
M-x org-version
is trying to locate your org-mode installation and determine if it was
installed from git. It assumes that if a .git directory exists then it
has a git repository it can interrogate for the specific git version
information.
It seems your git repository has tag references but they don't point at
valid objects in the git repository.
Regards,
Bernt
david@adboyd.com (J. David Boyd) writes:
> When I type org-version, I get a shell-command window opened, and this:
>
> error: refs/heads/master does not point to a valid object!
> error: refs/remotes/origin/HEAD does not point to a valid object!
> error: refs/remotes/origin/add-recursion-to-org-publish does not point to a valid object!
> error: refs/remotes/origin/beamer does not point to a valid object!
> error: refs/remotes/origin/emacs23 does not point to a valid object!
> error: refs/remotes/origin/experimental does not point to a valid object!
> error: refs/remotes/origin/experimental-code-for-the-new-export-engine does not point to a valid object!
> error: refs/remotes/origin/master does not point to a valid object!
> error: refs/remotes/origin/mobile-support does not point to a valid object!
> error: refs/remotes/origin/org-plot-doc does not point to a valid object!
> error: refs/remotes/origin/support-for-mobile-sync does not point to a valid object!
> error: refs/tags/5.23a does not point to a valid object!
> error: refs/tags/rel519 does not point to a valid object!
> error: refs/tags/release_ does not point to a valid object!
> error: refs/tags/release_4.12a does not point to a valid object!
> error: refs/tags/release_4.13 does not point to a valid object!
> error: refs/tags/release_4.19a does not point to a valid object!
> error: refs/tags/release_4.19b does not point to a valid object!
> error: refs/tags/release_4.20 does not point to a valid object!
> error: refs/tags/release_4.21 does not point to a valid object!
> error: refs/tags/release_4.22 does not point to a valid object!
> error: refs/tags/release_4.23 does not point to a valid object!
> error: refs/tags/release_4.24 does not point to a valid object!
> error: refs/tags/release_4.26 does not point to a valid object!
> error: refs/tags/release_4.27 does not point to a valid object!
> error: refs/tags/release_4.28 does not point to a valid object!
> error: refs/tags/release_4.29 does not point to a valid object!
> error: refs/tags/release_4.30 does not point to a valid object!
> error: refs/tags/release_4.33 does not point to a valid object!
> error: refs/tags/release_4.34 does not point to a valid object!
> error: refs/tags/release_4.36 does not point to a valid object!
> error: refs/tags/release_4.37 does not point to a valid object!
> error: refs/tags/release_4.40 does not point to a valid object!
> error: refs/tags/release_4.41 does not point to a valid object!
> error: refs/tags/release_4.42 does not point to a valid object!
> error: refs/tags/release_4.43 does not point to a valid object!
> error: refs/tags/release_4.44 does not point to a valid object!
> error: refs/tags/release_4.45 does not point to a valid object!
> error: refs/tags/release_4.46 does not point to a valid object!
> error: refs/tags/release_4.48 does not point to a valid object!
> error: refs/tags/release_4.50 does not point to a valid object!
> error: refs/tags/release_4.51 does not point to a valid object!
> error: refs/tags/release_4.52 does not point to a valid object!
> error: refs/tags/release_4.53 does not point to a valid object!
> error: refs/tags/release_4.54 does not point to a valid object!
> error: refs/tags/release_4.55 does not point to a valid object!
> error: refs/tags/release_4.56 does not point to a valid object!
> error: refs/tags/release_4.57 does not point to a valid object!
> error: refs/tags/release_4.58 does not point to a valid object!
> error: refs/tags/release_4.59 does not point to a valid object!
> error: refs/tags/release_4.60 does not point to a valid object!
> error: refs/tags/release_4.61 does not point to a valid object!
> error: refs/tags/release_4.62 does not point to a valid object!
> error: refs/tags/release_4.64 does not point to a valid object!
> error: refs/tags/release_4.65 does not point to a valid object!
> error: refs/tags/release_4.66 does not point to a valid object!
> error: refs/tags/release_4.67 does not point to a valid object!
> error: refs/tags/release_4.68 does not point to a valid object!
> error: refs/tags/release_4.69 does not point to a valid object!
> error: refs/tags/release_4.70 does not point to a valid object!
> error: refs/tags/release_4.71 does not point to a valid object!
> error: refs/tags/release_4.72 does not point to a valid object!
> error: refs/tags/release_4.74 does not point to a valid object!
> error: refs/tags/release_4.75 does not point to a valid object!
> error: refs/tags/release_4.76 does not point to a valid object!
> error: refs/tags/release_4.77 does not point to a valid object!
> error: refs/tags/release_4.78 does not point to a valid object!
> error: refs/tags/release_4.79 does not point to a valid object!
> error: refs/tags/release_5.01 does not point to a valid object!
> error: refs/tags/release_5.01b does not point to a valid object!
> error: refs/tags/release_5.02 does not point to a valid object!
> error: refs/tags/release_5.03 does not point to a valid object!
> error: refs/tags/release_5.03n does not point to a valid object!
> error: refs/tags/release_5.04 does not point to a valid object!
> error: refs/tags/release_5.05 does not point to a valid object!
> error: refs/tags/release_5.06 does not point to a valid object!
> error: refs/tags/release_5.06b does not point to a valid object!
> error: refs/tags/release_5.06c does not point to a valid object!
> error: refs/tags/release_5.06d does not point to a valid object!
> error: refs/tags/release_5.06e does not point to a valid object!
> error: refs/tags/release_5.07 does not point to a valid object!
> error: refs/tags/release_5.07a does not point to a valid object!
> error: refs/tags/release_5.10a does not point to a valid object!
> error: refs/tags/release_5.10b does not point to a valid object!
> error: refs/tags/release_5.11 does not point to a valid object!
> error: refs/tags/release_5.11b does not point to a valid object!
> error: refs/tags/release_5.12 does not point to a valid object!
> error: refs/tags/release_5.12b does not point to a valid object!
> error: refs/tags/release_5.12c does not point to a valid object!
> error: refs/tags/release_5.13 does not point to a valid object!
> error: refs/tags/release_5.13a does not point to a valid object!
> error: refs/tags/release_5.13c does not point to a valid object!
> error: refs/tags/release_5.13d does not point to a valid object!
> error: refs/tags/release_5.13e does not point to a valid object!
> error: refs/tags/release_5.13g does not point to a valid object!
> error: refs/tags/release_5.13h does not point to a valid object!
> error: refs/tags/release_5.13i does not point to a valid object!
> error: refs/tags/release_5.14 does not point to a valid object!
> error: refs/tags/release_5.15 does not point to a valid object!
> error: refs/tags/release_5.15a does not point to a valid object!
> error: refs/tags/release_5.16 does not point to a valid object!
> error: refs/tags/release_5.16a does not point to a valid object!
> error: refs/tags/release_5.16b does not point to a valid object!
> error: refs/tags/release_5.17 does not point to a valid object!
> error: refs/tags/release_5.17a does not point to a valid object!
> error: refs/tags/release_5.18 does not point to a valid object!
> error: refs/tags/release_5.18a does not point to a valid object!
> error: refs/tags/release_5.19 does not point to a valid object!
> error: refs/tags/release_5.19a does not point to a valid object!
> error: refs/tags/release_5.20 does not point to a valid object!
> error: refs/tags/release_5.21 does not point to a valid object!
> error: refs/tags/release_5.22 does not point to a valid object!
> error: refs/tags/release_5.22a does not point to a valid object!
> error: refs/tags/release_5.23a does not point to a valid object!
> error: refs/tags/release_6.01 does not point to a valid object!
> error: refs/tags/release_6.01a does not point to a valid object!
> error: refs/tags/release_6.01b does not point to a valid object!
> error: refs/tags/release_6.01c does not point to a valid object!
> error: refs/tags/release_6.02 does not point to a valid object!
> error: refs/tags/release_6.02a does not point to a valid object!
> error: refs/tags/release_6.02b does not point to a valid object!
> error: refs/tags/release_6.03 does not point to a valid object!
> error: refs/tags/release_6.04 does not point to a valid object!
> error: refs/tags/release_6.04a does not point to a valid object!
> error: refs/tags/release_6.04b does not point to a valid object!
> error: refs/tags/release_6.04c does not point to a valid object!
> error: refs/tags/release_6.05 does not point to a valid object!
> error: refs/tags/release_6.05a does not point to a valid object!
> error: refs/tags/release_6.05b does not point to a valid object!
> error: refs/tags/release_6.06 does not point to a valid object!
> error: refs/tags/release_6.06a does not point to a valid object!
> error: refs/tags/release_6.06b does not point to a valid object!
> error: refs/tags/release_6.07 does not point to a valid object!
> error: refs/tags/release_6.07a does not point to a valid object!
> error: refs/tags/release_6.07b does not point to a valid object!
> error: refs/tags/release_6.08 does not point to a valid object!
> error: refs/tags/release_6.08a does not point to a valid object!
> error: refs/tags/release_6.08c does not point to a valid object!
> error: refs/tags/release_6.09 does not point to a valid object!
> error: refs/tags/release_6.09a does not point to a valid object!
> error: refs/tags/release_6.10 does not point to a valid object!
> error: refs/tags/release_6.10a does not point to a valid object!
> error: refs/tags/release_6.10b does not point to a valid object!
> error: refs/tags/release_6.10c does not point to a valid object!
> error: refs/tags/release_6.11 does not point to a valid object!
> error: refs/tags/release_6.11a does not point to a valid object!
> error: refs/tags/release_6.11b does not point to a valid object!
> error: refs/tags/release_6.11c does not point to a valid object!
> error: refs/tags/release_6.12 does not point to a valid object!
> error: refs/tags/release_6.12a does not point to a valid object!
> error: refs/tags/release_6.12b does not point to a valid object!
> error: refs/tags/release_6.13 does not point to a valid object!
> error: refs/tags/release_6.13a does not point to a valid object!
> error: refs/tags/release_6.14 does not point to a valid object!
> error: refs/tags/release_6.15 does not point to a valid object!
> error: refs/tags/release_6.15a does not point to a valid object!
> error: refs/tags/release_6.15b does not point to a valid object!
> error: refs/tags/release_6.15c does not point to a valid object!
> error: refs/tags/release_6.15d does not point to a valid object!
> error: refs/tags/release_6.15f does not point to a valid object!
> error: refs/tags/release_6.16 does not point to a valid object!
> error: refs/tags/release_6.16a does not point to a valid object!
> error: refs/tags/release_6.16b does not point to a valid object!
> error: refs/tags/release_6.16c does not point to a valid object!
> error: refs/tags/release_6.17 does not point to a valid object!
> error: refs/tags/release_6.17a does not point to a valid object!
> error: refs/tags/release_6.17b does not point to a valid object!
> error: refs/tags/release_6.17c does not point to a valid object!
> error: refs/tags/release_6.18 does not point to a valid object!
> error: refs/tags/release_6.18a does not point to a valid object!
> error: refs/tags/release_6.18b does not point to a valid object!
> error: refs/tags/release_6.18c does not point to a valid object!
> error: refs/tags/release_6.19 does not point to a valid object!
> error: refs/tags/release_6.19a does not point to a valid object!
> error: refs/tags/release_6.19b does not point to a valid object!
> error: refs/tags/release_6.19c does not point to a valid object!
> error: refs/tags/release_6.19d does not point to a valid object!
> error: refs/tags/release_6.19e does not point to a valid object!
> error: refs/tags/release_6.20 does not point to a valid object!
> error: refs/tags/release_6.20a does not point to a valid object!
> error: refs/tags/release_6.20b does not point to a valid object!
> error: refs/tags/release_6.20c does not point to a valid object!
> error: refs/tags/release_6.20d does not point to a valid object!
> error: refs/tags/release_6.20e does not point to a valid object!
> error: refs/tags/release_6.20f does not point to a valid object!
> error: refs/tags/release_6.20g does not point to a valid object!
> error: refs/tags/release_6.20h does not point to a valid object!
> error: refs/tags/release_6.20i does not point to a valid object!
> error: refs/tags/release_6.21 does not point to a valid object!
> error: refs/tags/release_6.21a does not point to a valid object!
> error: refs/tags/release_6.21b does not point to a valid object!
> error: refs/tags/release_6.22 does not point to a valid object!
> error: refs/tags/release_6.22a does not point to a valid object!
> error: refs/tags/release_6.22b does not point to a valid object!
> error: refs/tags/release_6.23 does not point to a valid object!
> error: refs/tags/release_6.23a does not point to a valid object!
> error: refs/tags/release_6.23b does not point to a valid object!
> error: refs/tags/release_6.24 does not point to a valid object!
> error: refs/tags/release_6.24a does not point to a valid object!
> error: refs/tags/release_6.24b does not point to a valid object!
> error: refs/tags/release_6.24c does not point to a valid object!
> error: refs/tags/release_6.25 does not point to a valid object!
> error: refs/tags/release_6.25a does not point to a valid object!
> error: refs/tags/release_6.25b does not point to a valid object!
> error: refs/tags/release_6.25c does not point to a valid object!
> error: refs/tags/release_6.25d does not point to a valid object!
> error: refs/tags/release_6.25e does not point to a valid object!
> error: refs/tags/release_6.25f does not point to a valid object!
> error: refs/tags/release_6.26 does not point to a valid object!
> error: refs/tags/release_6.26a does not point to a valid object!
> error: refs/tags/release_6.26b does not point to a valid object!
> error: refs/tags/release_6.26c does not point to a valid object!
> error: refs/tags/release_6.26d does not point to a valid object!
> error: refs/tags/release_6.27 does not point to a valid object!
> error: refs/tags/release_6.27a does not point to a valid object!
> error: refs/tags/release_6.28 does not point to a valid object!
> error: refs/tags/release_6.28a does not point to a valid object!
> error: refs/tags/release_6.28b does not point to a valid object!
> error: refs/tags/release_6.28c does not point to a valid object!
> error: refs/tags/release_6.28d does not point to a valid object!
> error: refs/tags/release_6.28e does not point to a valid object!
> error: refs/tags/release_6.29 does not point to a valid object!
> error: refs/tags/release_6.29a does not point to a valid object!
> error: refs/tags/release_6.29b does not point to a valid object!
> error: refs/tags/release_6.29c does not point to a valid object!
> error: refs/tags/release_6.30 does not point to a valid object!
> error: refs/tags/release_6.30a does not point to a valid object!
> error: refs/tags/release_6.30b does not point to a valid object!
> error: refs/tags/release_6.30c does not point to a valid object!
> error: refs/tags/release_6.30d does not point to a valid object!
> error: refs/tags/release_6.30e does not point to a valid object!
> error: refs/tags/release_6.31 does not point to a valid object!
> error: refs/tags/release_6.32 does not point to a valid object!
> error: refs/tags/release_6.32a does not point to a valid object!
> error: refs/tags/release_6.32b does not point to a valid object!
> error: refs/tags/release_6.33 does not point to a valid object!
> error: refs/tags/release_6.33a does not point to a valid object!
> error: refs/tags/release_6.33b does not point to a valid object!
> error: refs/tags/release_6.33c does not point to a valid object!
> error: refs/tags/release_6.33d does not point to a valid object!
> error: refs/tags/release_6.33e does not point to a valid object!
> error: refs/tags/release_6.33f does not point to a valid object!
> error: refs/tags/release_6.34 does not point to a valid object!
> error: refs/tags/release_6.34a does not point to a valid object!
> error: refs/tags/release_6.34b does not point to a valid object!
> error: refs/tags/release_6.34c does not point to a valid object!
> error: refs/tags/test_5.21_tagging does not point to a valid object!
> fatal: No names found, cannot describe anything.
>
>
>
> I just updated to emacs 23.2, and I"m using the latest org, downloaded
> with
>
> wget http://orgmode.org/org-latest.tar.gz
>
>
>
> Anyone else seen this? Is this an ORG bug, or an EMACS bug?
>
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: bug?
2010-05-12 13:35 ` bug? Bernt Hansen
@ 2010-05-12 14:32 ` J. David Boyd
0 siblings, 0 replies; 44+ messages in thread
From: J. David Boyd @ 2010-05-12 14:32 UTC (permalink / raw)
To: emacs-orgmode
Hmm, did it the same way I always do. I just extract it, and then
compile it, then use it.
But thanks for the info. I deleted the .gitignore file and the .git
directory, and now no more errors.
Dave
Bernt Hansen <bernt@norang.ca> writes:
> Hi David,
>
> It's org-mode and not Emacs.
>
> This is output from 'git describe' trying to identify the git version
> you are running. Did you unpack that archive in a directory with a git
> archive (containing a .git subdirectory?)
>
> Does
>
> (locate-library "org")
>
> return some other location than where you unpacked this archive and does
> it have a .git subdirectory?
>
> M-x org-version
> is trying to locate your org-mode installation and determine if it was
> installed from git. It assumes that if a .git directory exists then it
> has a git repository it can interrogate for the specific git version
> information.
>
> It seems your git repository has tag references but they don't point at
> valid objects in the git repository.
>
> Regards,
> Bernt
>
>
> david@adboyd.com (J. David Boyd) writes:
>
>> When I type org-version, I get a shell-command window opened, and this:
>>
>> error: refs/heads/master does not point to a valid object!
>> error: refs/remotes/origin/HEAD does not point to a valid object!
>> error: refs/remotes/origin/add-recursion-to-org-publish does not point to a valid object!
>> error: refs/remotes/origin/beamer does not point to a valid object!
>> error: refs/remotes/origin/emacs23 does not point to a valid object!
>> error: refs/remotes/origin/experimental does not point to a valid object!
>> error: refs/remotes/origin/experimental-code-for-the-new-export-engine does not point to a valid object!
>> error: refs/remotes/origin/master does not point to a valid object!
>> error: refs/remotes/origin/mobile-support does not point to a valid object!
>> error: refs/remotes/origin/org-plot-doc does not point to a valid object!
>> error: refs/remotes/origin/support-for-mobile-sync does not point to a valid object!
>> error: refs/tags/5.23a does not point to a valid object!
>> error: refs/tags/rel519 does not point to a valid object!
>> error: refs/tags/release_ does not point to a valid object!
>> error: refs/tags/release_4.12a does not point to a valid object!
>> error: refs/tags/release_4.13 does not point to a valid object!
>> error: refs/tags/release_4.19a does not point to a valid object!
>> error: refs/tags/release_4.19b does not point to a valid object!
>> error: refs/tags/release_4.20 does not point to a valid object!
>> error: refs/tags/release_4.21 does not point to a valid object!
>> error: refs/tags/release_4.22 does not point to a valid object!
>> error: refs/tags/release_4.23 does not point to a valid object!
>> error: refs/tags/release_4.24 does not point to a valid object!
>> error: refs/tags/release_4.26 does not point to a valid object!
>> error: refs/tags/release_4.27 does not point to a valid object!
>> error: refs/tags/release_4.28 does not point to a valid object!
>> error: refs/tags/release_4.29 does not point to a valid object!
>> error: refs/tags/release_4.30 does not point to a valid object!
>> error: refs/tags/release_4.33 does not point to a valid object!
>> error: refs/tags/release_4.34 does not point to a valid object!
>> error: refs/tags/release_4.36 does not point to a valid object!
>> error: refs/tags/release_4.37 does not point to a valid object!
>> error: refs/tags/release_4.40 does not point to a valid object!
>> error: refs/tags/release_4.41 does not point to a valid object!
>> error: refs/tags/release_4.42 does not point to a valid object!
>> error: refs/tags/release_4.43 does not point to a valid object!
>> error: refs/tags/release_4.44 does not point to a valid object!
>> error: refs/tags/release_4.45 does not point to a valid object!
>> error: refs/tags/release_4.46 does not point to a valid object!
>> error: refs/tags/release_4.48 does not point to a valid object!
>> error: refs/tags/release_4.50 does not point to a valid object!
>> error: refs/tags/release_4.51 does not point to a valid object!
>> error: refs/tags/release_4.52 does not point to a valid object!
>> error: refs/tags/release_4.53 does not point to a valid object!
>> error: refs/tags/release_4.54 does not point to a valid object!
>> error: refs/tags/release_4.55 does not point to a valid object!
>> error: refs/tags/release_4.56 does not point to a valid object!
>> error: refs/tags/release_4.57 does not point to a valid object!
>> error: refs/tags/release_4.58 does not point to a valid object!
>> error: refs/tags/release_4.59 does not point to a valid object!
>> error: refs/tags/release_4.60 does not point to a valid object!
>> error: refs/tags/release_4.61 does not point to a valid object!
>> error: refs/tags/release_4.62 does not point to a valid object!
>> error: refs/tags/release_4.64 does not point to a valid object!
>> error: refs/tags/release_4.65 does not point to a valid object!
>> error: refs/tags/release_4.66 does not point to a valid object!
>> error: refs/tags/release_4.67 does not point to a valid object!
>> error: refs/tags/release_4.68 does not point to a valid object!
>> error: refs/tags/release_4.69 does not point to a valid object!
>> error: refs/tags/release_4.70 does not point to a valid object!
>> error: refs/tags/release_4.71 does not point to a valid object!
>> error: refs/tags/release_4.72 does not point to a valid object!
>> error: refs/tags/release_4.74 does not point to a valid object!
>> error: refs/tags/release_4.75 does not point to a valid object!
>> error: refs/tags/release_4.76 does not point to a valid object!
>> error: refs/tags/release_4.77 does not point to a valid object!
>> error: refs/tags/release_4.78 does not point to a valid object!
>> error: refs/tags/release_4.79 does not point to a valid object!
>> error: refs/tags/release_5.01 does not point to a valid object!
>> error: refs/tags/release_5.01b does not point to a valid object!
>> error: refs/tags/release_5.02 does not point to a valid object!
>> error: refs/tags/release_5.03 does not point to a valid object!
>> error: refs/tags/release_5.03n does not point to a valid object!
>> error: refs/tags/release_5.04 does not point to a valid object!
>> error: refs/tags/release_5.05 does not point to a valid object!
>> error: refs/tags/release_5.06 does not point to a valid object!
>> error: refs/tags/release_5.06b does not point to a valid object!
>> error: refs/tags/release_5.06c does not point to a valid object!
>> error: refs/tags/release_5.06d does not point to a valid object!
>> error: refs/tags/release_5.06e does not point to a valid object!
>> error: refs/tags/release_5.07 does not point to a valid object!
>> error: refs/tags/release_5.07a does not point to a valid object!
>> error: refs/tags/release_5.10a does not point to a valid object!
>> error: refs/tags/release_5.10b does not point to a valid object!
>> error: refs/tags/release_5.11 does not point to a valid object!
>> error: refs/tags/release_5.11b does not point to a valid object!
>> error: refs/tags/release_5.12 does not point to a valid object!
>> error: refs/tags/release_5.12b does not point to a valid object!
>> error: refs/tags/release_5.12c does not point to a valid object!
>> error: refs/tags/release_5.13 does not point to a valid object!
>> error: refs/tags/release_5.13a does not point to a valid object!
>> error: refs/tags/release_5.13c does not point to a valid object!
>> error: refs/tags/release_5.13d does not point to a valid object!
>> error: refs/tags/release_5.13e does not point to a valid object!
>> error: refs/tags/release_5.13g does not point to a valid object!
>> error: refs/tags/release_5.13h does not point to a valid object!
>> error: refs/tags/release_5.13i does not point to a valid object!
>> error: refs/tags/release_5.14 does not point to a valid object!
>> error: refs/tags/release_5.15 does not point to a valid object!
>> error: refs/tags/release_5.15a does not point to a valid object!
>> error: refs/tags/release_5.16 does not point to a valid object!
>> error: refs/tags/release_5.16a does not point to a valid object!
>> error: refs/tags/release_5.16b does not point to a valid object!
>> error: refs/tags/release_5.17 does not point to a valid object!
>> error: refs/tags/release_5.17a does not point to a valid object!
>> error: refs/tags/release_5.18 does not point to a valid object!
>> error: refs/tags/release_5.18a does not point to a valid object!
>> error: refs/tags/release_5.19 does not point to a valid object!
>> error: refs/tags/release_5.19a does not point to a valid object!
>> error: refs/tags/release_5.20 does not point to a valid object!
>> error: refs/tags/release_5.21 does not point to a valid object!
>> error: refs/tags/release_5.22 does not point to a valid object!
>> error: refs/tags/release_5.22a does not point to a valid object!
>> error: refs/tags/release_5.23a does not point to a valid object!
>> error: refs/tags/release_6.01 does not point to a valid object!
>> error: refs/tags/release_6.01a does not point to a valid object!
>> error: refs/tags/release_6.01b does not point to a valid object!
>> error: refs/tags/release_6.01c does not point to a valid object!
>> error: refs/tags/release_6.02 does not point to a valid object!
>> error: refs/tags/release_6.02a does not point to a valid object!
>> error: refs/tags/release_6.02b does not point to a valid object!
>> error: refs/tags/release_6.03 does not point to a valid object!
>> error: refs/tags/release_6.04 does not point to a valid object!
>> error: refs/tags/release_6.04a does not point to a valid object!
>> error: refs/tags/release_6.04b does not point to a valid object!
>> error: refs/tags/release_6.04c does not point to a valid object!
>> error: refs/tags/release_6.05 does not point to a valid object!
>> error: refs/tags/release_6.05a does not point to a valid object!
>> error: refs/tags/release_6.05b does not point to a valid object!
>> error: refs/tags/release_6.06 does not point to a valid object!
>> error: refs/tags/release_6.06a does not point to a valid object!
>> error: refs/tags/release_6.06b does not point to a valid object!
>> error: refs/tags/release_6.07 does not point to a valid object!
>> error: refs/tags/release_6.07a does not point to a valid object!
>> error: refs/tags/release_6.07b does not point to a valid object!
>> error: refs/tags/release_6.08 does not point to a valid object!
>> error: refs/tags/release_6.08a does not point to a valid object!
>> error: refs/tags/release_6.08c does not point to a valid object!
>> error: refs/tags/release_6.09 does not point to a valid object!
>> error: refs/tags/release_6.09a does not point to a valid object!
>> error: refs/tags/release_6.10 does not point to a valid object!
>> error: refs/tags/release_6.10a does not point to a valid object!
>> error: refs/tags/release_6.10b does not point to a valid object!
>> error: refs/tags/release_6.10c does not point to a valid object!
>> error: refs/tags/release_6.11 does not point to a valid object!
>> error: refs/tags/release_6.11a does not point to a valid object!
>> error: refs/tags/release_6.11b does not point to a valid object!
>> error: refs/tags/release_6.11c does not point to a valid object!
>> error: refs/tags/release_6.12 does not point to a valid object!
>> error: refs/tags/release_6.12a does not point to a valid object!
>> error: refs/tags/release_6.12b does not point to a valid object!
>> error: refs/tags/release_6.13 does not point to a valid object!
>> error: refs/tags/release_6.13a does not point to a valid object!
>> error: refs/tags/release_6.14 does not point to a valid object!
>> error: refs/tags/release_6.15 does not point to a valid object!
>> error: refs/tags/release_6.15a does not point to a valid object!
>> error: refs/tags/release_6.15b does not point to a valid object!
>> error: refs/tags/release_6.15c does not point to a valid object!
>> error: refs/tags/release_6.15d does not point to a valid object!
>> error: refs/tags/release_6.15f does not point to a valid object!
>> error: refs/tags/release_6.16 does not point to a valid object!
>> error: refs/tags/release_6.16a does not point to a valid object!
>> error: refs/tags/release_6.16b does not point to a valid object!
>> error: refs/tags/release_6.16c does not point to a valid object!
>> error: refs/tags/release_6.17 does not point to a valid object!
>> error: refs/tags/release_6.17a does not point to a valid object!
>> error: refs/tags/release_6.17b does not point to a valid object!
>> error: refs/tags/release_6.17c does not point to a valid object!
>> error: refs/tags/release_6.18 does not point to a valid object!
>> error: refs/tags/release_6.18a does not point to a valid object!
>> error: refs/tags/release_6.18b does not point to a valid object!
>> error: refs/tags/release_6.18c does not point to a valid object!
>> error: refs/tags/release_6.19 does not point to a valid object!
>> error: refs/tags/release_6.19a does not point to a valid object!
>> error: refs/tags/release_6.19b does not point to a valid object!
>> error: refs/tags/release_6.19c does not point to a valid object!
>> error: refs/tags/release_6.19d does not point to a valid object!
>> error: refs/tags/release_6.19e does not point to a valid object!
>> error: refs/tags/release_6.20 does not point to a valid object!
>> error: refs/tags/release_6.20a does not point to a valid object!
>> error: refs/tags/release_6.20b does not point to a valid object!
>> error: refs/tags/release_6.20c does not point to a valid object!
>> error: refs/tags/release_6.20d does not point to a valid object!
>> error: refs/tags/release_6.20e does not point to a valid object!
>> error: refs/tags/release_6.20f does not point to a valid object!
>> error: refs/tags/release_6.20g does not point to a valid object!
>> error: refs/tags/release_6.20h does not point to a valid object!
>> error: refs/tags/release_6.20i does not point to a valid object!
>> error: refs/tags/release_6.21 does not point to a valid object!
>> error: refs/tags/release_6.21a does not point to a valid object!
>> error: refs/tags/release_6.21b does not point to a valid object!
>> error: refs/tags/release_6.22 does not point to a valid object!
>> error: refs/tags/release_6.22a does not point to a valid object!
>> error: refs/tags/release_6.22b does not point to a valid object!
>> error: refs/tags/release_6.23 does not point to a valid object!
>> error: refs/tags/release_6.23a does not point to a valid object!
>> error: refs/tags/release_6.23b does not point to a valid object!
>> error: refs/tags/release_6.24 does not point to a valid object!
>> error: refs/tags/release_6.24a does not point to a valid object!
>> error: refs/tags/release_6.24b does not point to a valid object!
>> error: refs/tags/release_6.24c does not point to a valid object!
>> error: refs/tags/release_6.25 does not point to a valid object!
>> error: refs/tags/release_6.25a does not point to a valid object!
>> error: refs/tags/release_6.25b does not point to a valid object!
>> error: refs/tags/release_6.25c does not point to a valid object!
>> error: refs/tags/release_6.25d does not point to a valid object!
>> error: refs/tags/release_6.25e does not point to a valid object!
>> error: refs/tags/release_6.25f does not point to a valid object!
>> error: refs/tags/release_6.26 does not point to a valid object!
>> error: refs/tags/release_6.26a does not point to a valid object!
>> error: refs/tags/release_6.26b does not point to a valid object!
>> error: refs/tags/release_6.26c does not point to a valid object!
>> error: refs/tags/release_6.26d does not point to a valid object!
>> error: refs/tags/release_6.27 does not point to a valid object!
>> error: refs/tags/release_6.27a does not point to a valid object!
>> error: refs/tags/release_6.28 does not point to a valid object!
>> error: refs/tags/release_6.28a does not point to a valid object!
>> error: refs/tags/release_6.28b does not point to a valid object!
>> error: refs/tags/release_6.28c does not point to a valid object!
>> error: refs/tags/release_6.28d does not point to a valid object!
>> error: refs/tags/release_6.28e does not point to a valid object!
>> error: refs/tags/release_6.29 does not point to a valid object!
>> error: refs/tags/release_6.29a does not point to a valid object!
>> error: refs/tags/release_6.29b does not point to a valid object!
>> error: refs/tags/release_6.29c does not point to a valid object!
>> error: refs/tags/release_6.30 does not point to a valid object!
>> error: refs/tags/release_6.30a does not point to a valid object!
>> error: refs/tags/release_6.30b does not point to a valid object!
>> error: refs/tags/release_6.30c does not point to a valid object!
>> error: refs/tags/release_6.30d does not point to a valid object!
>> error: refs/tags/release_6.30e does not point to a valid object!
>> error: refs/tags/release_6.31 does not point to a valid object!
>> error: refs/tags/release_6.32 does not point to a valid object!
>> error: refs/tags/release_6.32a does not point to a valid object!
>> error: refs/tags/release_6.32b does not point to a valid object!
>> error: refs/tags/release_6.33 does not point to a valid object!
>> error: refs/tags/release_6.33a does not point to a valid object!
>> error: refs/tags/release_6.33b does not point to a valid object!
>> error: refs/tags/release_6.33c does not point to a valid object!
>> error: refs/tags/release_6.33d does not point to a valid object!
>> error: refs/tags/release_6.33e does not point to a valid object!
>> error: refs/tags/release_6.33f does not point to a valid object!
>> error: refs/tags/release_6.34 does not point to a valid object!
>> error: refs/tags/release_6.34a does not point to a valid object!
>> error: refs/tags/release_6.34b does not point to a valid object!
>> error: refs/tags/release_6.34c does not point to a valid object!
>> error: refs/tags/test_5.21_tagging does not point to a valid object!
>> fatal: No names found, cannot describe anything.
>>
>>
>>
>> I just updated to emacs 23.2, and I"m using the latest org, downloaded
>> with
>>
>> wget http://orgmode.org/org-latest.tar.gz
>>
>>
>>
>> Anyone else seen this? Is this an ORG bug, or an EMACS bug?
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 44+ messages in thread
* Bug?
@ 2012-12-04 16:53 Charles
2012-12-04 19:12 ` Bug? Achim Gratz
0 siblings, 1 reply; 44+ messages in thread
From: Charles @ 2012-12-04 16:53 UTC (permalink / raw)
To: emacs-orgmode Mode; +Cc: Stromeko
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
System etc.
Windows 7 Home Premium, Service Pack 1, 64 bit
Cygwin 1.7.17-1
GNU Emacs 24.2.1(i686-pc-cygwin, GTK+ Version 2.24.11) of 2012-08-27 on
fiona
Org-mode version 7.9.2 (release_7.9.2-646-g664217 @
/home/Charlie/elisp/org-mode/lisp/)
updated using the following make autoloads && make update
Up until the past week or two, whenever I updated from git, even when no
.el files were changed, the org manual was always "remade", "retypeset"
and other info or TeX files as well.
For my most recent update I decided to create a log (attached) and
noticed permission denied for some files concerning org.t2d.
Also attached is a list of files in the ~/elsip/org-mode/doc directory.
I have cc'd Achim Gratz in case this is a cygwin related problem (at
least it is my impression that Achim also uses cygwin .) I have not
downloaded emacs-24.2.90-1; however all other packages were updated
(including the AucTeX).
If this is not a bug, just point me in the correct direction so I can
solve this.
TIA.
Charlie Millar
[-- Attachment #2: elisporgmodedoc.org --]
[-- Type: text/plain, Size: 1174 bytes --]
total 3363
drwxr-xr-x+ 1 Charlie None 0 Dec 4 11:30 ./
drwxr-xr-x+ 1 Charlie None 0 Dec 4 11:30 ../
-rw-r--r-- 1 Charlie None 1850 Sep 13 18:19 .aspell.org.conf
-rw-r--r-- 1 Charlie None 10 Sep 13 18:19 .nosearch
-rw-r--r-- 1 Charlie None 617 Sep 13 18:19 dir
-rw-r--r-- 1 Charlie None 6953 Sep 13 18:19 Documentation_Standards.org
-rw-r--r-- 1 Charlie None 0 Dec 4 11:30 elisporgmodedoc.org
-rw-r--r-- 1 Charlie None 2070 Sep 13 18:19 Makefile
-rw-r--r-- 1 Charlie None 889948 Dec 4 08:24 org
-rw-r--r-- 1 Charlie None 1380703 Dec 4 08:24 org.html
drwxr-xr-x+ 1 Administrators SYSTEM 0 Nov 29 08:34 org.t2d/
-rw-r--r-- 1 Charlie None 716581 Nov 30 12:22 org.texi
-rw-r--r-- 1 Charlie None 23761 Oct 26 12:32 orgcard.tex
-rw-r--r-- 1 Charlie None 99657 Oct 2 07:26 orgguide.texi
-rw-r--r-- 1 Charlie None 108 Dec 4 08:24 org-version.inc
-rw-r--r-- 1 Charlie None 1325 Sep 13 18:19 pdflayout.sty
-rw-r--r-- 1 Charlie None 285317 Sep 13 18:19 texinfo.tex
[-- Attachment #3: uporglog.org --]
[-- Type: text/plain, Size: 37159 bytes --]
Tue, Dec 04, 2012 8:24:36 AM
make -C lisp autoloads
make[1]: Entering directory `/home/Charlie/elisp/org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
org-version: 7.9.2 (release_7.9.2-646-g664217)
Loading /home/Charlie/elisp/org-mode/lisp/org-compat.el (source)...
Loading /home/Charlie/elisp/org-mode/mk/org-fixup.el (source)...
Saving file /home/Charlie/elisp/org-mode/lisp/org-version.el...
Loading vc-git...
Wrote /home/Charlie/elisp/org-mode/lisp/org-version.el
org-loaddefs: 7.9.2 (release_7.9.2-646-g664217)
Loading /home/Charlie/elisp/org-mode/lisp/org-compat.el (source)...
Loading /home/Charlie/elisp/org-mode/mk/org-fixup.el (source)...
Generating autoloads for ob-C.el...
Generating autoloads for ob-C.el...done
Generating autoloads for ob-R.el...
Generating autoloads for ob-R.el...done
Generating autoloads for ob-asymptote.el...
Generating autoloads for ob-asymptote.el...done
Generating autoloads for ob-awk.el...
Generating autoloads for ob-awk.el...done
Generating autoloads for ob-calc.el...
Generating autoloads for ob-calc.el...done
Generating autoloads for ob-clojure.el...
Generating autoloads for ob-clojure.el...done
Generating autoloads for ob-comint.el...
Generating autoloads for ob-comint.el...done
Generating autoloads for ob-css.el...
Generating autoloads for ob-css.el...done
Generating autoloads for ob-ditaa.el...
Generating autoloads for ob-ditaa.el...done
Generating autoloads for ob-dot.el...
Generating autoloads for ob-dot.el...done
Generating autoloads for ob-emacs-lisp.el...
Generating autoloads for ob-emacs-lisp.el...done
Generating autoloads for ob-eval.el...
Generating autoloads for ob-eval.el...done
Generating autoloads for ob-exp.el...
Generating autoloads for ob-exp.el...done
Generating autoloads for ob-fortran.el...
Generating autoloads for ob-fortran.el...done
Generating autoloads for ob-gnuplot.el...
Generating autoloads for ob-gnuplot.el...done
Generating autoloads for ob-haskell.el...
Generating autoloads for ob-haskell.el...done
Generating autoloads for ob-io.el...
Generating autoloads for ob-io.el...done
Generating autoloads for ob-java.el...
Generating autoloads for ob-java.el...done
Generating autoloads for ob-js.el...
Generating autoloads for ob-js.el...done
Making generated-autoload-file local to *autoload-file* while let-bound!
Generating autoloads for ob-keys.el...
Generating autoloads for ob-keys.el...done
Generating autoloads for ob-latex.el...
Generating autoloads for ob-latex.el...done
Generating autoloads for ob-ledger.el...
Generating autoloads for ob-ledger.el...done
Generating autoloads for ob-lilypond.el...
Generating autoloads for ob-lilypond.el...done
Generating autoloads for ob-lisp.el...
Generating autoloads for ob-lisp.el...done
Generating autoloads for ob-lob.el...
Generating autoloads for ob-lob.el...done
Generating autoloads for ob-makefile.el...
Generating autoloads for ob-makefile.el...done
Generating autoloads for ob-matlab.el...
Generating autoloads for ob-matlab.el...done
Generating autoloads for ob-maxima.el...
Generating autoloads for ob-maxima.el...done
Generating autoloads for ob-mscgen.el...
Generating autoloads for ob-mscgen.el...done
Generating autoloads for ob-ocaml.el...
Generating autoloads for ob-ocaml.el...done
Generating autoloads for ob-octave.el...
Generating autoloads for ob-octave.el...done
Generating autoloads for ob-org.el...
Generating autoloads for ob-org.el...done
Generating autoloads for ob-perl.el...
Generating autoloads for ob-perl.el...done
Generating autoloads for ob-picolisp.el...
Generating autoloads for ob-picolisp.el...done
Generating autoloads for ob-plantuml.el...
Generating autoloads for ob-plantuml.el...done
Generating autoloads for ob-python.el...
Generating autoloads for ob-python.el...done
Generating autoloads for ob-ref.el...
Generating autoloads for ob-ref.el...done
Generating autoloads for ob-ruby.el...
Generating autoloads for ob-ruby.el...done
Generating autoloads for ob-sass.el...
Generating autoloads for ob-sass.el...done
Generating autoloads for ob-scala.el...
Generating autoloads for ob-scala.el...done
Generating autoloads for ob-scheme.el...
Generating autoloads for ob-scheme.el...done
Generating autoloads for ob-screen.el...
Generating autoloads for ob-screen.el...done
Generating autoloads for ob-sh.el...
Generating autoloads for ob-sh.el...done
Generating autoloads for ob-shen.el...
Generating autoloads for ob-shen.el...done
Generating autoloads for ob-sql.el...
Generating autoloads for ob-sql.el...done
Generating autoloads for ob-sqlite.el...
Generating autoloads for ob-sqlite.el...done
Generating autoloads for ob-table.el...
Generating autoloads for ob-table.el...done
Generating autoloads for ob-tangle.el...
Generating autoloads for ob-tangle.el...done
Generating autoloads for ob.el...
Generating autoloads for ob.el...done
Generating autoloads for org-agenda.el...
Generating autoloads for org-agenda.el...done
Generating autoloads for org-archive.el...
Generating autoloads for org-archive.el...done
Generating autoloads for org-ascii.el...
Generating autoloads for org-ascii.el...done
Generating autoloads for org-attach.el...
Generating autoloads for org-attach.el...done
Generating autoloads for org-bbdb.el...
Generating autoloads for org-bbdb.el...done
Generating autoloads for org-beamer.el...
Generating autoloads for org-beamer.el...done
Generating autoloads for org-bibtex.el...
Generating autoloads for org-bibtex.el...done
Generating autoloads for org-capture.el...
Generating autoloads for org-capture.el...done
Generating autoloads for org-clock.el...
Generating autoloads for org-clock.el...done
Generating autoloads for org-colview-xemacs.el...
Generating autoloads for org-colview-xemacs.el...done
Generating autoloads for org-colview.el...
Generating autoloads for org-colview.el...done
Generating autoloads for org-compat.el...
Generating autoloads for org-compat.el...done
Generating autoloads for org-crypt.el...
Generating autoloads for org-crypt.el...done
Generating autoloads for org-ctags.el...
Generating autoloads for org-ctags.el...done
Generating autoloads for org-datetree.el...
Generating autoloads for org-datetree.el...done
Generating autoloads for org-docbook.el...
Generating autoloads for org-docbook.el...done
Generating autoloads for org-docview.el...
Generating autoloads for org-docview.el...done
Generating autoloads for org-element.el...
Generating autoloads for org-element.el...done
Generating autoloads for org-entities.el...
Generating autoloads for org-entities.el...done
Generating autoloads for org-eshell.el...
Generating autoloads for org-eshell.el...done
Generating autoloads for org-exp.el...
Generating autoloads for org-exp.el...done
Generating autoloads for org-faces.el...
Generating autoloads for org-faces.el...done
Generating autoloads for org-feed.el...
Generating autoloads for org-feed.el...done
Generating autoloads for org-footnote.el...
Generating autoloads for org-footnote.el...done
Generating autoloads for org-freemind.el...
Generating autoloads for org-freemind.el...done
Generating autoloads for org-gnus.el...
Generating autoloads for org-gnus.el...done
Generating autoloads for org-habit.el...
Generating autoloads for org-habit.el...done
Generating autoloads for org-html.el...
Generating autoloads for org-html.el...done
Generating autoloads for org-icalendar.el...
Generating autoloads for org-icalendar.el...done
Generating autoloads for org-id.el...
Generating autoloads for org-id.el...done
Generating autoloads for org-indent.el...
Generating autoloads for org-indent.el...done
Generating autoloads for org-info.el...
Generating autoloads for org-info.el...done
Generating autoloads for org-inlinetask.el...
Generating autoloads for org-inlinetask.el...done
Generating autoloads for org-install.el...
Generating autoloads for org-install.el...done
Generating autoloads for org-irc.el...
Generating autoloads for org-irc.el...done
Generating autoloads for org-jsinfo.el...
Generating autoloads for org-jsinfo.el...done
Generating autoloads for org-latex.el...
Generating autoloads for org-latex.el...done
Generating autoloads for org-list.el...
Generating autoloads for org-list.el...done
Generating autoloads for org-lparse.el...
Generating autoloads for org-lparse.el...done
Generating autoloads for org-mac-message.el...
Generating autoloads for org-mac-message.el...done
Generating autoloads for org-macs.el...
Generating autoloads for org-macs.el...done
Generating autoloads for org-mew.el...
Generating autoloads for org-mew.el...done
Generating autoloads for org-mhe.el...
Generating autoloads for org-mhe.el...done
Generating autoloads for org-mks.el...
Generating autoloads for org-mks.el...done
Generating autoloads for org-mobile.el...
Generating autoloads for org-mobile.el...done
Generating autoloads for org-mouse.el...
Generating autoloads for org-mouse.el...done
Generating autoloads for org-odt.el...
Generating autoloads for org-odt.el...done
Generating autoloads for org-pcomplete.el...
Generating autoloads for org-pcomplete.el...done
Generating autoloads for org-plot.el...
Generating autoloads for org-plot.el...done
Generating autoloads for org-protocol.el...
Generating autoloads for org-protocol.el...done
Generating autoloads for org-publish.el...
Generating autoloads for org-publish.el...done
Generating autoloads for org-remember.el...
Generating autoloads for org-remember.el...done
Generating autoloads for org-rmail.el...
Generating autoloads for org-rmail.el...done
Generating autoloads for org-special-blocks.el...
Generating autoloads for org-special-blocks.el...done
Generating autoloads for org-src.el...
Generating autoloads for org-src.el...done
Generating autoloads for org-table.el...
Generating autoloads for org-table.el...done
Generating autoloads for org-taskjuggler.el...
Generating autoloads for org-taskjuggler.el...done
Generating autoloads for org-timer.el...
Generating autoloads for org-timer.el...done
Generating autoloads for org-version.el...
Generating autoloads for org-version.el...done
Generating autoloads for org-vm.el...
Generating autoloads for org-vm.el...done
Generating autoloads for org-w3m.el...
Generating autoloads for org-w3m.el...done
Generating autoloads for org-wl.el...
Generating autoloads for org-wl.el...done
Generating autoloads for org-xoxo.el...
Generating autoloads for org-xoxo.el...done
Generating autoloads for org.el...
Generating autoloads for org.el...done
Saving file /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el...
Loading vc-git...
Wrote /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/lisp'
git remote update
Fetching origin
git pull
Already up-to-date.
make -C doc clean; make -C lisp clean;
make[1]: Entering directory `/home/Charlie/elisp/org-mode/doc'
rm -f org *.pdf *.html *_letter.tex org-version.inc \
*.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs \
*.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/doc'
make[1]: Entering directory `/home/Charlie/elisp/org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
rm -f *.elc
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/lisp'
make -C doc all; make -C etc all; make -C lisp all;
make[1]: Entering directory `/home/Charlie/elisp/org-mode/doc'
org-version: 7.9.2 (release_7.9.2-646-g664217)
makeinfo --no-split org.texi -o org
makeinfo --html --number-sections --no-split -o org.html org.texi
texi2pdf --batch --clean org.texi
mkdir: cannot create directory `/home/Charlie/elisp/org-mode/doc/org.t2d/pdf/bak': Permission denied
/usr/bin/texi2dvi: cannot create directory: /home/Charlie/elisp/org-mode/doc/org.t2d/pdf/bak
rm: cannot remove `/home/Charlie/elisp/org-mode/doc/org.t2d/pdf/build/org.vrs': Permission denied
rm: cannot remove `/home/Charlie/elisp/org-mode/doc/org.t2d/version_test/txiversion.err': Permission denied
rm: cannot remove `/home/Charlie/elisp/org-mode/doc/org.t2d/version_test/txiversion.log': Permission denied
rm: cannot remove `/home/Charlie/elisp/org-mode/doc/org.t2d/version_test/txiversion.out': Permission denied
rm: cannot remove `/home/Charlie/elisp/org-mode/doc/org.t2d/version_test/txiversion.tex': Permission denied
Makefile:60: recipe for target `org.pdf' failed
make[1]: *** [org.pdf] Error 1
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/doc'
make[1]: Entering directory `/home/Charlie/elisp/org-mode/etc'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/etc'
make[1]: Entering directory `/home/Charlie/elisp/org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
org-version: 7.9.2 (release_7.9.2-646-g664217)
Loading /home/Charlie/elisp/org-mode/lisp/org-compat.el (source)...
Loading /home/Charlie/elisp/org-mode/mk/org-fixup.el (source)...
Saving file /home/Charlie/elisp/org-mode/lisp/org-version.el...
Loading vc-git...
Wrote /home/Charlie/elisp/org-mode/lisp/org-version.el
org-loaddefs: 7.9.2 (release_7.9.2-646-g664217)
Loading /home/Charlie/elisp/org-mode/lisp/org-compat.el (source)...
Loading /home/Charlie/elisp/org-mode/mk/org-fixup.el (source)...
Generating autoloads for ob-C.el...
Generating autoloads for ob-C.el...done
Generating autoloads for ob-R.el...
Generating autoloads for ob-R.el...done
Generating autoloads for ob-asymptote.el...
Generating autoloads for ob-asymptote.el...done
Generating autoloads for ob-awk.el...
Generating autoloads for ob-awk.el...done
Generating autoloads for ob-calc.el...
Generating autoloads for ob-calc.el...done
Generating autoloads for ob-clojure.el...
Generating autoloads for ob-clojure.el...done
Generating autoloads for ob-comint.el...
Generating autoloads for ob-comint.el...done
Generating autoloads for ob-css.el...
Generating autoloads for ob-css.el...done
Generating autoloads for ob-ditaa.el...
Generating autoloads for ob-ditaa.el...done
Generating autoloads for ob-dot.el...
Generating autoloads for ob-dot.el...done
Generating autoloads for ob-emacs-lisp.el...
Generating autoloads for ob-emacs-lisp.el...done
Generating autoloads for ob-eval.el...
Generating autoloads for ob-eval.el...done
Generating autoloads for ob-exp.el...
Generating autoloads for ob-exp.el...done
Generating autoloads for ob-fortran.el...
Generating autoloads for ob-fortran.el...done
Generating autoloads for ob-gnuplot.el...
Generating autoloads for ob-gnuplot.el...done
Generating autoloads for ob-haskell.el...
Generating autoloads for ob-haskell.el...done
Generating autoloads for ob-io.el...
Generating autoloads for ob-io.el...done
Generating autoloads for ob-java.el...
Generating autoloads for ob-java.el...done
Generating autoloads for ob-js.el...
Generating autoloads for ob-js.el...done
Making generated-autoload-file local to *autoload-file* while let-bound!
Generating autoloads for ob-keys.el...
Generating autoloads for ob-keys.el...done
Generating autoloads for ob-latex.el...
Generating autoloads for ob-latex.el...done
Generating autoloads for ob-ledger.el...
Generating autoloads for ob-ledger.el...done
Generating autoloads for ob-lilypond.el...
Generating autoloads for ob-lilypond.el...done
Generating autoloads for ob-lisp.el...
Generating autoloads for ob-lisp.el...done
Generating autoloads for ob-lob.el...
Generating autoloads for ob-lob.el...done
Generating autoloads for ob-makefile.el...
Generating autoloads for ob-makefile.el...done
Generating autoloads for ob-matlab.el...
Generating autoloads for ob-matlab.el...done
Generating autoloads for ob-maxima.el...
Generating autoloads for ob-maxima.el...done
Generating autoloads for ob-mscgen.el...
Generating autoloads for ob-mscgen.el...done
Generating autoloads for ob-ocaml.el...
Generating autoloads for ob-ocaml.el...done
Generating autoloads for ob-octave.el...
Generating autoloads for ob-octave.el...done
Generating autoloads for ob-org.el...
Generating autoloads for ob-org.el...done
Generating autoloads for ob-perl.el...
Generating autoloads for ob-perl.el...done
Generating autoloads for ob-picolisp.el...
Generating autoloads for ob-picolisp.el...done
Generating autoloads for ob-plantuml.el...
Generating autoloads for ob-plantuml.el...done
Generating autoloads for ob-python.el...
Generating autoloads for ob-python.el...done
Generating autoloads for ob-ref.el...
Generating autoloads for ob-ref.el...done
Generating autoloads for ob-ruby.el...
Generating autoloads for ob-ruby.el...done
Generating autoloads for ob-sass.el...
Generating autoloads for ob-sass.el...done
Generating autoloads for ob-scala.el...
Generating autoloads for ob-scala.el...done
Generating autoloads for ob-scheme.el...
Generating autoloads for ob-scheme.el...done
Generating autoloads for ob-screen.el...
Generating autoloads for ob-screen.el...done
Generating autoloads for ob-sh.el...
Generating autoloads for ob-sh.el...done
Generating autoloads for ob-shen.el...
Generating autoloads for ob-shen.el...done
Generating autoloads for ob-sql.el...
Generating autoloads for ob-sql.el...done
Generating autoloads for ob-sqlite.el...
Generating autoloads for ob-sqlite.el...done
Generating autoloads for ob-table.el...
Generating autoloads for ob-table.el...done
Generating autoloads for ob-tangle.el...
Generating autoloads for ob-tangle.el...done
Generating autoloads for ob.el...
Generating autoloads for ob.el...done
Generating autoloads for org-agenda.el...
Generating autoloads for org-agenda.el...done
Generating autoloads for org-archive.el...
Generating autoloads for org-archive.el...done
Generating autoloads for org-ascii.el...
Generating autoloads for org-ascii.el...done
Generating autoloads for org-attach.el...
Generating autoloads for org-attach.el...done
Generating autoloads for org-bbdb.el...
Generating autoloads for org-bbdb.el...done
Generating autoloads for org-beamer.el...
Generating autoloads for org-beamer.el...done
Generating autoloads for org-bibtex.el...
Generating autoloads for org-bibtex.el...done
Generating autoloads for org-capture.el...
Generating autoloads for org-capture.el...done
Generating autoloads for org-clock.el...
Generating autoloads for org-clock.el...done
Generating autoloads for org-colview-xemacs.el...
Generating autoloads for org-colview-xemacs.el...done
Generating autoloads for org-colview.el...
Generating autoloads for org-colview.el...done
Generating autoloads for org-compat.el...
Generating autoloads for org-compat.el...done
Generating autoloads for org-crypt.el...
Generating autoloads for org-crypt.el...done
Generating autoloads for org-ctags.el...
Generating autoloads for org-ctags.el...done
Generating autoloads for org-datetree.el...
Generating autoloads for org-datetree.el...done
Generating autoloads for org-docbook.el...
Generating autoloads for org-docbook.el...done
Generating autoloads for org-docview.el...
Generating autoloads for org-docview.el...done
Generating autoloads for org-element.el...
Generating autoloads for org-element.el...done
Generating autoloads for org-entities.el...
Generating autoloads for org-entities.el...done
Generating autoloads for org-eshell.el...
Generating autoloads for org-eshell.el...done
Generating autoloads for org-exp.el...
Generating autoloads for org-exp.el...done
Generating autoloads for org-faces.el...
Generating autoloads for org-faces.el...done
Generating autoloads for org-feed.el...
Generating autoloads for org-feed.el...done
Generating autoloads for org-footnote.el...
Generating autoloads for org-footnote.el...done
Generating autoloads for org-freemind.el...
Generating autoloads for org-freemind.el...done
Generating autoloads for org-gnus.el...
Generating autoloads for org-gnus.el...done
Generating autoloads for org-habit.el...
Generating autoloads for org-habit.el...done
Generating autoloads for org-html.el...
Generating autoloads for org-html.el...done
Generating autoloads for org-icalendar.el...
Generating autoloads for org-icalendar.el...done
Generating autoloads for org-id.el...
Generating autoloads for org-id.el...done
Generating autoloads for org-indent.el...
Generating autoloads for org-indent.el...done
Generating autoloads for org-info.el...
Generating autoloads for org-info.el...done
Generating autoloads for org-inlinetask.el...
Generating autoloads for org-inlinetask.el...done
Generating autoloads for org-install.el...
Generating autoloads for org-install.el...done
Generating autoloads for org-irc.el...
Generating autoloads for org-irc.el...done
Generating autoloads for org-jsinfo.el...
Generating autoloads for org-jsinfo.el...done
Generating autoloads for org-latex.el...
Generating autoloads for org-latex.el...done
Generating autoloads for org-list.el...
Generating autoloads for org-list.el...done
Generating autoloads for org-lparse.el...
Generating autoloads for org-lparse.el...done
Generating autoloads for org-mac-message.el...
Generating autoloads for org-mac-message.el...done
Generating autoloads for org-macs.el...
Generating autoloads for org-macs.el...done
Generating autoloads for org-mew.el...
Generating autoloads for org-mew.el...done
Generating autoloads for org-mhe.el...
Generating autoloads for org-mhe.el...done
Generating autoloads for org-mks.el...
Generating autoloads for org-mks.el...done
Generating autoloads for org-mobile.el...
Generating autoloads for org-mobile.el...done
Generating autoloads for org-mouse.el...
Generating autoloads for org-mouse.el...done
Generating autoloads for org-odt.el...
Generating autoloads for org-odt.el...done
Generating autoloads for org-pcomplete.el...
Generating autoloads for org-pcomplete.el...done
Generating autoloads for org-plot.el...
Generating autoloads for org-plot.el...done
Generating autoloads for org-protocol.el...
Generating autoloads for org-protocol.el...done
Generating autoloads for org-publish.el...
Generating autoloads for org-publish.el...done
Generating autoloads for org-remember.el...
Generating autoloads for org-remember.el...done
Generating autoloads for org-rmail.el...
Generating autoloads for org-rmail.el...done
Generating autoloads for org-special-blocks.el...
Generating autoloads for org-special-blocks.el...done
Generating autoloads for org-src.el...
Generating autoloads for org-src.el...done
Generating autoloads for org-table.el...
Generating autoloads for org-table.el...done
Generating autoloads for org-taskjuggler.el...
Generating autoloads for org-taskjuggler.el...done
Generating autoloads for org-timer.el...
Generating autoloads for org-timer.el...done
Generating autoloads for org-version.el...
Generating autoloads for org-version.el...done
Generating autoloads for org-vm.el...
Generating autoloads for org-vm.el...done
Generating autoloads for org-w3m.el...
Generating autoloads for org-w3m.el...done
Generating autoloads for org-wl.el...
Generating autoloads for org-wl.el...done
Generating autoloads for org-xoxo.el...
Generating autoloads for org-xoxo.el...done
Generating autoloads for org.el...
Generating autoloads for org.el...done
Saving file /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el...
Loading vc-git...
Wrote /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el
make compile-dirall
==================== dirall ====================
make[2]: Entering directory `/home/Charlie/elisp/org-mode/lisp'
Checking /home/Charlie/elisp/org-mode/lisp...
Compiling /home/Charlie/elisp/org-mode/lisp/ob-C.el...
In org-babel-C-execute:
ob-C.el:108:9:Warning: reference to free variable `result-params'
Wrote /home/Charlie/elisp/org-mode/lisp/ob-C.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-R.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-R.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-asymptote.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-asymptote.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-awk.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-awk.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-calc.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-calc.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-clojure.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-clojure.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-comint.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-comint.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-css.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-css.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-ditaa.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-ditaa.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-dot.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-dot.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-emacs-lisp.el...
In org-babel-execute:emacs-lisp:
ob-emacs-lisp.el:64:29:Warning: reference to free variable `result-params'
Wrote /home/Charlie/elisp/org-mode/lisp/ob-emacs-lisp.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-eval.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-eval.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-exp.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-exp.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-fortran.el...
In org-babel-execute:fortran:
ob-fortran.el:64:9:Warning: reference to free variable `result-params'
Wrote /home/Charlie/elisp/org-mode/lisp/ob-fortran.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-gnuplot.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-gnuplot.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-haskell.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-haskell.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-io.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-io.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-java.el...
In org-babel-execute:java:
ob-java.el:60:9:Warning: reference to free variable `result-params'
Wrote /home/Charlie/elisp/org-mode/lisp/ob-java.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-js.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-js.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-keys.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-keys.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-latex.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-latex.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-ledger.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-ledger.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-lilypond.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-lilypond.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-lisp.el...
In org-babel-execute:lisp:
ob-lisp.el:80:14:Warning: reference to free variable `result-params'
Wrote /home/Charlie/elisp/org-mode/lisp/ob-lisp.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-lob.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-lob.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-makefile.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-makefile.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-matlab.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-matlab.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-maxima.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-maxima.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-mscgen.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-mscgen.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-ocaml.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-ocaml.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-octave.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-octave.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-org.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-org.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-perl.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-perl.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-picolisp.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-picolisp.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-plantuml.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-plantuml.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-python.el...
In toplevel form:
ob-python.el:55:1:Warning: defcustom for `org-babel-python-hline-to' fails to
specify containing group
ob-python.el:58:1:Warning: defcustom for `org-babel-python-None-to' fails to
specify containing group
Wrote /home/Charlie/elisp/org-mode/lisp/ob-python.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-ref.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-ref.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-ruby.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-ruby.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-sass.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-sass.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-scala.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-scala.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-scheme.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-scheme.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-screen.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-screen.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-sh.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-sh.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-shen.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-shen.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-sql.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-sql.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-sqlite.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-sqlite.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-table.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-table.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob-tangle.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob-tangle.elc
Compiling /home/Charlie/elisp/org-mode/lisp/ob.el...
Wrote /home/Charlie/elisp/org-mode/lisp/ob.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-agenda.el...
Loading /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el (source)...
Wrote /home/Charlie/elisp/org-mode/lisp/org-agenda.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-archive.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-archive.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-ascii.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-ascii.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-attach.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-attach.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-bbdb.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-bbdb.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-beamer.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-beamer.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-bibtex.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-bibtex.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-capture.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-capture.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-clock.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-clock.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-colview-xemacs.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-colview-xemacs.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-colview.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-colview.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-compat.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-compat.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-crypt.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-crypt.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-ctags.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-ctags.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-datetree.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-datetree.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-docbook.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-docbook.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-docview.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-docview.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-element.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-element.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-entities.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-entities.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-eshell.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-eshell.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-exp.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-exp.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-faces.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-faces.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-feed.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-feed.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-footnote.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-footnote.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-freemind.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-freemind.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-gnus.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-gnus.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-habit.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-habit.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-html.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-html.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-icalendar.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-icalendar.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-id.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-id.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-indent.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-indent.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-info.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-info.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-inlinetask.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-inlinetask.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-install.el...
Compiling /home/Charlie/elisp/org-mode/lisp/org-irc.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-irc.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-jsinfo.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-jsinfo.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-latex.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-latex.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-list.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-list.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-loaddefs.el...
Compiling /home/Charlie/elisp/org-mode/lisp/org-lparse.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-lparse.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mac-message.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mac-message.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-macs.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-macs.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mew.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mew.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mhe.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mhe.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mks.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mks.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mobile.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mobile.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-mouse.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-mouse.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-odt.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-odt.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-pcomplete.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-pcomplete.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-plot.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-plot.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-protocol.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-protocol.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-publish.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-publish.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-remember.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-remember.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-rmail.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-rmail.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-special-blocks.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-special-blocks.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-src.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-src.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-table.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-table.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-taskjuggler.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-taskjuggler.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-timer.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-timer.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-version.el...
Compiling /home/Charlie/elisp/org-mode/lisp/org-vm.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-vm.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-w3m.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-w3m.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-wl.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-wl.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org-xoxo.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org-xoxo.elc
Compiling /home/Charlie/elisp/org-mode/lisp/org.el...
Wrote /home/Charlie/elisp/org-mode/lisp/org.elc
Done (Total of 111 files compiled, 3 skipped)
make[2]: Leaving directory `/home/Charlie/elisp/org-mode/lisp'
make[1]: Leaving directory `/home/Charlie/elisp/org-mode/lisp'
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2012-12-04 16:53 Bug? Charles
@ 2012-12-04 19:12 ` Achim Gratz
2012-12-05 1:20 ` Bug? Charles
0 siblings, 1 reply; 44+ messages in thread
From: Achim Gratz @ 2012-12-04 19:12 UTC (permalink / raw)
To: emacs-orgmode
Charles writes:
> I have cc'd Achim Gratz in case this is a cygwin related problem (at
> least it is my impression that Achim also uses cygwin .)
Yes, at work.
> -rw-r--r-- 1 Charlie None 1380703 Dec 4 08:24 org.html
> drwxr-xr-x+ 1 Administrators SYSTEM 0 Nov 29 08:34 org.t2d/
The problem is most likely that the org.t2d directory was created with
administrator rights and you seem to now be trying to use it as a normal
user. However, you do not have the necessary access rights (you can
read the directory entries and cd into it, but can't create files, as
far as Cygwin is concerned) and apparently the ACL for that directory
(which you didn't show) also is not adding file creation rights. So if
you remove that directory things should work better I think.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2012-12-04 19:12 ` Bug? Achim Gratz
@ 2012-12-05 1:20 ` Charles
0 siblings, 0 replies; 44+ messages in thread
From: Charles @ 2012-12-05 1:20 UTC (permalink / raw)
To: emacs-orgmode
On 12/4/2012 2:12 PM, Achim Gratz wrote:
> Charles writes:
>> I have cc'd Achim Gratz in case this is a cygwin related problem (at
>> least it is my impression that Achim also uses cygwin .)
> Yes, at work.
>
>> -rw-r--r-- 1 Charlie None 1380703 Dec 4 08:24 org.html
>> drwxr-xr-x+ 1 Administrators SYSTEM 0 Nov 29 08:34 org.t2d/
> The problem is most likely that the org.t2d directory was created with
> administrator rights and you seem to now be trying to use it as a normal
> user. However, you do not have the necessary access rights (you can
> read the directory entries and cd into it, but can't create files, as
> far as Cygwin is concerned) and apparently the ACL for that directory
> (which you didn't show) also is not adding file creation rights. So if
> you remove that directory things should work better I think.
>
You are correct. Thanks for the advice.
Charlie
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug:
2014-02-06 11:38 ` Bastien
@ 2014-03-06 17:32 ` Paul Stansell
0 siblings, 0 replies; 44+ messages in thread
From: Paul Stansell @ 2014-03-06 17:32 UTC (permalink / raw)
To: emacs-orgmode
Yes, it's fixed now, thanks.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Bug??
@ 2014-05-06 14:47 Susan Cragin
2014-05-06 15:28 ` Bug?? Maurice
2014-05-07 16:15 ` Bug?? Achim Gratz
0 siblings, 2 replies; 44+ messages in thread
From: Susan Cragin @ 2014-05-06 14:47 UTC (permalink / raw)
To: Emacs-orgmode list
[-- Attachment #1: Type: text/html, Size: 1098 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug??
2014-05-06 14:47 Bug?? Susan Cragin
@ 2014-05-06 15:28 ` Maurice
2014-05-06 21:30 ` Bug?? Suvayu Ali
2014-05-07 16:15 ` Bug?? Achim Gratz
1 sibling, 1 reply; 44+ messages in thread
From: Maurice @ 2014-05-06 15:28 UTC (permalink / raw)
To: emacs-orgmode
Hi,
Susan Cragin <susancragin@earthlink.net> écrivit :
> Hi. I got error messages on my compiles relating to the documents, starting
> perhaps yesterday or the day before.
> I re-downloaded the repo and updated my depends files, to no avail.
> This is just FYI.
>
> Done (Total of 108 files compiled, 3 skipped)
> make[2]: Leaving directory '/home/susan/org-mode/lisp'
> make[1]: Leaving directory '/home/susan/org-mode/lisp'
> make -C doc info
> make[1]: Entering directory '/home/susan/org-mode/doc'
> org-version: 8.2.6 (release_8.2.6-945-gc80509)
> makeinfo --no-split org.texi -o org
***************************************
> make[1]: makeinfo: Command not found
***************************************
> Makefile:55: recipe for target 'org' failed
> make[1]: *** [org] Error 127
> make[1]: Leaving directory '/home/susan/org-mode/doc'
> mk/targets.mk:126: recipe for target 'info' failed
> make: *** [info] Error 2
This is not an org-mode problem, now on your machine you are missing the program
makeinfo.
Maurice
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug??
2014-05-06 15:28 ` Bug?? Maurice
@ 2014-05-06 21:30 ` Suvayu Ali
0 siblings, 0 replies; 44+ messages in thread
From: Suvayu Ali @ 2014-05-06 21:30 UTC (permalink / raw)
To: emacs-orgmode
On Tue, May 06, 2014 at 05:28:23PM +0200, Maurice wrote:
> Susan Cragin <susancragin@earthlink.net> écrivit :
>
> > make[1]: Entering directory '/home/susan/org-mode/doc'
> > org-version: 8.2.6 (release_8.2.6-945-gc80509)
> > makeinfo --no-split org.texi -o org
> ***************************************
> > make[1]: makeinfo: Command not found
> ***************************************
> > Makefile:55: recipe for target 'org' failed
> > make[1]: *** [org] Error 127
> > make[1]: Leaving directory '/home/susan/org-mode/doc'
> > mk/targets.mk:126: recipe for target 'info' failed
> > make: *** [info] Error 2
>
> This is not an org-mode problem, now on your machine you are missing the program
> makeinfo.
And usually makeinfo is provided by the texinfo package.
--
Suvayu
Open source is the future. It sets us free.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug??
2014-05-06 14:47 Bug?? Susan Cragin
2014-05-06 15:28 ` Bug?? Maurice
@ 2014-05-07 16:15 ` Achim Gratz
1 sibling, 0 replies; 44+ messages in thread
From: Achim Gratz @ 2014-05-07 16:15 UTC (permalink / raw)
To: emacs-orgmode
Susan Cragin writes:
> Hi. I got error messages on my compiles relating to the documents,
> starting perhaps yesterday or the day before.
If this really worked before, then the most likely culprit is that
you've changed your PATH in the last two days or so.
> make[1]: makeinfo: Command not found
You should re-arrange your PATH that makeinfo can be found again or you
need to change local.mk to like MAKEINFO=/full/path/to/makeinfo so that
it can be executed even if not found in path.
Regards
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
^ permalink raw reply [flat|nested] 44+ messages in thread
* bug?
@ 2017-06-20 13:38 John Kitchin
2017-06-29 14:36 ` bug? Nicolas Goaziou
0 siblings, 1 reply; 44+ messages in thread
From: John Kitchin @ 2017-06-20 13:38 UTC (permalink / raw)
To: Org-mode
I think there is a bug with invisible edits.
In org 8.2.10 if I set this:
(setq org-catch-invisible-edits 'smart) ; or show
and have org-toggle-pretty-entities active, then if there is no headline
before point, with the point here:
NH^{3}
^
I get outline-back-to-heading: Before first heading if I try to type anything.
I also get this same error in org 9.0.7. It only happens with the 3
wrapped in {}.
That seems like a bug to me.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: bug?
2017-06-20 13:38 bug? John Kitchin
@ 2017-06-29 14:36 ` Nicolas Goaziou
2017-06-30 0:53 ` bug? John Kitchin
0 siblings, 1 reply; 44+ messages in thread
From: Nicolas Goaziou @ 2017-06-29 14:36 UTC (permalink / raw)
To: John Kitchin; +Cc: Org-mode
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I think there is a bug with invisible edits.
>
> In org 8.2.10 if I set this:
>
> (setq org-catch-invisible-edits 'smart) ; or show
>
> and have org-toggle-pretty-entities active, then if there is no headline
> before point, with the point here:
>
> NH^{3}
> ^
>
> I get outline-back-to-heading: Before first heading if I try to type anything.
>
> I also get this same error in org 9.0.7. It only happens with the 3
> wrapped in {}.
>
> That seems like a bug to me.
Fixed, somewhat.
I think `org-check-before-invisible-edit' deserves some discussion about
its specifications. As-is, it contains logic errors. For example, if you
try to edit text near invisible text and you happen to have invisible
custom properties somewhere else in the buffer, the properties are going
to be made visible but not the invisible text at point.
I would be happy to fix this, but need to think about what is expected,
e.g. when we are editing something near an invisible link or, as in your
example, sub/superscript.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: bug?
2017-06-29 14:36 ` bug? Nicolas Goaziou
@ 2017-06-30 0:53 ` John Kitchin
2017-07-01 12:30 ` bug? Nicolas Goaziou
0 siblings, 1 reply; 44+ messages in thread
From: John Kitchin @ 2017-06-30 0:53 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: Org-mode
All I thought should happen is that the invisible text adjacent to the
point would be edited (except for the {}). Other than the edge case
where there is no first headline, it seems to work ok as far as I can
tell.
Nicolas Goaziou writes:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> I think there is a bug with invisible edits.
>>
>> In org 8.2.10 if I set this:
>>
>> (setq org-catch-invisible-edits 'smart) ; or show
>>
>> and have org-toggle-pretty-entities active, then if there is no headline
>> before point, with the point here:
>>
>> NH^{3}
>> ^
>>
>> I get outline-back-to-heading: Before first heading if I try to type anything.
>>
>> I also get this same error in org 9.0.7. It only happens with the 3
>> wrapped in {}.
>>
>> That seems like a bug to me.
>
> Fixed, somewhat.
>
> I think `org-check-before-invisible-edit' deserves some discussion about
> its specifications. As-is, it contains logic errors. For example, if you
> try to edit text near invisible text and you happen to have invisible
> custom properties somewhere else in the buffer, the properties are going
> to be made visible but not the invisible text at point.
>
> I would be happy to fix this, but need to think about what is expected,
> e.g. when we are editing something near an invisible link or, as in your
> example, sub/superscript.
>
> Regards,
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: bug?
2017-06-30 0:53 ` bug? John Kitchin
@ 2017-07-01 12:30 ` Nicolas Goaziou
0 siblings, 0 replies; 44+ messages in thread
From: Nicolas Goaziou @ 2017-07-01 12:30 UTC (permalink / raw)
To: John Kitchin; +Cc: Org-mode
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> All I thought should happen is that the invisible text adjacent to the
> point would be edited (except for the {}). Other than the edge case
> where there is no first headline, it seems to work ok as far as I can
> tell.
Oops. I thought I had fixed it, but it wasn't the case. Done now.
My question is still open: what could this function do, if anything,
close to invisible text per properties (i.e., a link or
sub/superscript)?
I'm not even sure there is something clever to do. A few months ago,
I wanted to solve the problem differently, and suggested to display
"[[path][desc]]" as "[desc]" instead of just "desc". It wasn't so well
received. Admittedly, it adds cruft to the buffer.
Someone suggested to have the link expand whenever the point was over
it, but it was a time-consuming process and it would cause the text to
jump around.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 44+ messages in thread
* Bug?
[not found] <875y9aciir.fsf.ref@yahoo.com>
@ 2023-05-03 1:26 ` Po Lu
2023-05-03 9:40 ` Bug? Mattias Engdegård
0 siblings, 1 reply; 44+ messages in thread
From: Po Lu @ 2023-05-03 1:26 UTC (permalink / raw)
To: emacs-devel
A bootstrap leads to:
Loading indent...
Loading emacs-lisp/cl-generic...
Loading simple...
Dropping text-properties while making string `Matches %s' pure
Is this not a subtle bug?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 1:26 ` Bug? Po Lu
@ 2023-05-03 9:40 ` Mattias Engdegård
2023-05-03 10:12 ` Bug? Mattias Engdegård
2023-05-03 11:23 ` Bug? Eli Zaretskii
0 siblings, 2 replies; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-03 9:40 UTC (permalink / raw)
To: Po Lu; +Cc: emacs-devel, Shynur Xie
3 maj 2023 kl. 03.26 skrev Po Lu <luangruo@yahoo.com>:
>
> A bootstrap leads to:
>
> Loading indent...
> Loading emacs-lisp/cl-generic...
> Loading simple...
> Dropping text-properties while making string `Matches %s' pure
Good catch, should work a little better now.
By the way, the standard blink-matching-paren-offscreen face (:foreground green) is terrible on a white background.
Don't we have an existing suitable face to inherit from? Would make it easier for theme authors, too.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 9:40 ` Bug? Mattias Engdegård
@ 2023-05-03 10:12 ` Mattias Engdegård
2023-05-03 11:24 ` Bug? Shynur Xie
2023-05-03 11:24 ` Bug? Eli Zaretskii
2023-05-03 11:23 ` Bug? Eli Zaretskii
1 sibling, 2 replies; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-03 10:12 UTC (permalink / raw)
To: Shynur Xie; +Cc: emacs-devel, Po Lu
> By the way, the standard blink-matching-paren-offscreen face (:foreground green) is terrible on a white background.
> Don't we have an existing suitable face to inherit from? Would make it easier for theme authors, too.
I also noticed that when the closing bracket is comprised of multiple characters, only the first character is high-lit using that face. For example, in shell-script-mode, when `esac` matches `case`, only the `c` in `case` is high-lit. Perhaps this new feature isn't quite finished yet.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 9:40 ` Bug? Mattias Engdegård
2023-05-03 10:12 ` Bug? Mattias Engdegård
@ 2023-05-03 11:23 ` Eli Zaretskii
1 sibling, 0 replies; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-03 11:23 UTC (permalink / raw)
To: Mattias Engdegård; +Cc: luangruo, emacs-devel, one.last.kiss
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 3 May 2023 11:40:04 +0200
> Cc: emacs-devel <emacs-devel@gnu.org>, Shynur Xie <one.last.kiss@outlook.com>
>
> By the way, the standard blink-matching-paren-offscreen face (:foreground green) is terrible on a white background.
Feel free to add a different default for bright background.
Thanks.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 10:12 ` Bug? Mattias Engdegård
@ 2023-05-03 11:24 ` Shynur Xie
2023-05-03 12:27 ` Bug? Mattias Engdegård
2023-05-03 11:24 ` Bug? Eli Zaretskii
1 sibling, 1 reply; 44+ messages in thread
From: Shynur Xie @ 2023-05-03 11:24 UTC (permalink / raw)
To: Mattias Engdegård; +Cc: emacs-devel, Po Lu
> From: Po Lu
> Subject: Bug?
> Date: Wed, 03 May 2023 09:26:20 +0800
>
> Is this not a subtle bug?
Thanks.
> From: Mattias Engdegård
> Subject: Re: Bug?
> Date: Wed, 3 May 2023 11:40:04 +0200
>
> Good catch, should work a little better now.
Thanks for fixing it.
> is terrible on a white background
Sorry for that.
> Don't we have an existing suitable face to inherit from?
Do you mean to inherit from those faces that set colors separately for
light and dark backgrounds? I hadn't thought about it before; it's a
good idea, I think.
> I also noticed that when the closing bracket is comprised of
> multiple characters, only the first character is high-lit using that
> face.
That is the original behavior of `blink-matching-open' -- it only
highlights the first character. (What you expected is provided by
`show-paren-mode'.) It uses `forward-sexp' to move point to the first
character (in your example, it's `c`), but `forward-sexp' doesn't
report the length of this keyword (i.e., `case`). I have no idea how
to implement highlighting for the entire matched keyword without
making many modifications.
BTW, if you want to give the function `blink-matching-open' the
semantic of highlighting the entire matched keyword, please change the
name of the function `blink-paren-open-paren-line-string' called by
`blink-matching-open', since `case` is not a parenthesis. Thanks.
--
shynur
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 10:12 ` Bug? Mattias Engdegård
2023-05-03 11:24 ` Bug? Shynur Xie
@ 2023-05-03 11:24 ` Eli Zaretskii
2023-05-03 11:26 ` Bug? Shynur Xie
` (2 more replies)
1 sibling, 3 replies; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-03 11:24 UTC (permalink / raw)
To: one.last.kiss, Mattias Engdegård; +Cc: emacs-devel, luangruo
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 3 May 2023 12:12:09 +0200
> Cc: emacs-devel <emacs-devel@gnu.org>, Po Lu <luangruo@yahoo.com>
>
> I also noticed that when the closing bracket is comprised of multiple characters, only the first character is high-lit using that face. For example, in shell-script-mode, when `esac` matches `case`, only the `c` in `case` is high-lit. Perhaps this new feature isn't quite finished yet.
Shynur, could you please fix this deficiency?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 11:24 ` Bug? Eli Zaretskii
@ 2023-05-03 11:26 ` Shynur Xie
2023-05-04 8:35 ` Bug? Shynur Xie
2023-05-04 20:57 ` Bug? Shynur Xie
2 siblings, 0 replies; 44+ messages in thread
From: Shynur Xie @ 2023-05-03 11:26 UTC (permalink / raw)
To: Eli Zaretskii, Mattias Engdegård
Cc: emacs-devel@gnu.org, luangruo@yahoo.com
> From: Eli Zaretskii
> Subject: Re: Bug?
> Date: Wednesday, May 3, 2023 7:24 PM
> To: Shynur Xie
>
> Shynur, could you please fix this deficiency?
I will try.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 11:24 ` Bug? Shynur Xie
@ 2023-05-03 12:27 ` Mattias Engdegård
2023-05-03 17:22 ` Bug? Juri Linkov
0 siblings, 1 reply; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-03 12:27 UTC (permalink / raw)
To: Shynur Xie; +Cc: emacs-devel, Po Lu
3 maj 2023 kl. 13.24 skrev Shynur Xie <one.last.kiss@outlook.com>:
>> Don't we have an existing suitable face to inherit from?
>
> Do you mean to inherit from those faces that set colors separately for
> light and dark backgrounds?
Yes, and it's much easier for the user to customise a single "highlight" face than dozens of them. There is a face literally named "highlight"; would that do? If so, maybe we don't even need a new face at all.
If you really want a new face that uses green text by default, something like
(defface blink-matching-paren-offscreen
- '((t :foreground "green"))
+ '((((class color) (background light))
+ :background "yellow")
+ (((class color) (background dark))
+ :foreground "green"))
would be an improvement. Full saturated green text pretty much requires a dark background.
>> I also noticed that when the closing bracket is comprised of
>> multiple characters, only the first character is high-lit using that
>> face.
>
> That is the original behavior of `blink-matching-open' -- it only
> highlights the first character. (What you expected is provided by
> `show-paren-mode'.)
Ah yes. In Emacs, there are always layers upon layers.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 12:27 ` Bug? Mattias Engdegård
@ 2023-05-03 17:22 ` Juri Linkov
0 siblings, 0 replies; 44+ messages in thread
From: Juri Linkov @ 2023-05-03 17:22 UTC (permalink / raw)
To: Mattias Engdegård; +Cc: Shynur Xie, emacs-devel, Po Lu
>>> Don't we have an existing suitable face to inherit from?
>>
>> Do you mean to inherit from those faces that set colors separately for
>> light and dark backgrounds?
>
> Yes, and it's much easier for the user to customise a single
> "highlight" face than dozens of them. There is a face literally named
> "highlight"; would that do? If so, maybe we don't even need a new
> face at all.
When the 'highlight' face is used, then no need to remove font-lock
properties. The highlighted paren with the green background
is clearly seen among font-lock faces.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 11:24 ` Bug? Eli Zaretskii
2023-05-03 11:26 ` Bug? Shynur Xie
@ 2023-05-04 8:35 ` Shynur Xie
2023-05-04 20:57 ` Bug? Shynur Xie
2 siblings, 0 replies; 44+ messages in thread
From: Shynur Xie @ 2023-05-04 8:35 UTC (permalink / raw)
To: Eli Zaretskii, Mattias Engdegård
Cc: emacs-devel@gnu.org, luangruo@yahoo.com
Hi, Eli.
In my last email, I mentioned that highlighting only 1 character is
the original behavior of the function `blink-matching-open':
> From: Shynur Xie <one.last.kiss@outlook.com>
> To: Mattias Engdegård
> Cc: emacs-devel; Po Lu
>
>> I also noticed that when the closing bracket is comprised of
>> multiple characters, only the first character is high-lit using
>> that face.
>
> That is the original behavior of `blink-matching-open' -- it only
> highlights the first character. (What you expected is provided by
> `show-paren-mode'.) It uses `forward-sexp' to move point to the
> first character (in your example, it's `c`), but `forward-sexp'
> doesn't report the length of this keyword (i.e., `case`).
I also find that, the mode `show-paren-mode' (which highlights an
entire matched keyword) also emits a message "Matches %s" which will
override what `blink-matching-open' does, when that mode's own option
`show-paren-context-when-offscreen' is t.
In conclusion, before my patch was installed, by default,
`blink-matching-open' highlighted only 1 matched character when that
character is on-screen; `show-paren-mode' highlighted the entire
keyword. But both of them didn't highlight the matched off-screen
openparen shown in the echo area. After my patch was installed,
`blink-matching-open' highlights the 1st character when that character
is off-screen, as well as how it does originally when the character is
on-screen.
So I'm now wondering, would it be better to write the functionality
(highlighting an entire matched keyword when it is shown in the echo
area) into <lisp/paren.el> instead of <lisp/simple.el> (and make it a
part of `show-paren-mode')? My opinion is, if `blink-matching-open'
highlights the entire matched keyword in the echo area, why doesn't it
also highlight an entire keyword that is on-screen? But if it does,
`blink-matching-open' and `show-paren-mode' will conflict/duplicate in
function/code. If we make that functionality a part of
`show-paren-mode', not only is behavioral consistency guaranteed in
all respects, but that functionality can simply reuse the logic/code
of `show-paren-mode'.
Any suggstion? Thanks.
--
shynur
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-03 11:24 ` Bug? Eli Zaretskii
2023-05-03 11:26 ` Bug? Shynur Xie
2023-05-04 8:35 ` Bug? Shynur Xie
@ 2023-05-04 20:57 ` Shynur Xie
2023-05-05 4:41 ` Bug? Eli Zaretskii
2023-05-06 10:44 ` Bug? Mattias Engdegård
2 siblings, 2 replies; 44+ messages in thread
From: Shynur Xie @ 2023-05-04 20:57 UTC (permalink / raw)
To: Eli Zaretskii, Mattias Engdegård
Cc: emacs-devel@gnu.org, luangruo@yahoo.com
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
> From: Eli Zaretskii
> Subject: Re: Bug?
> Date: Wed, 03 May 2023 14:24:49 +0300
>
>> I also noticed that when the closing bracket is comprised of
>> multiple characters, only the first character is high-lit using
>> that face. For example, in shell-script-mode, when `esac` matches
>> `case`, only the `c` in `case` is high-lit. Perhaps this new
>> feature isn't quite finished yet.
>
> Shynur, could you please fix this deficiency?
Patch is attached. To highlight the entire matched opening delimiter:
(show-paren-mode)
(setq blink-matching-paren-offscreen t
show-paren-context-when-offscreen t)
I also changed the function `blink-paren-open-paren-line-string':
Originally, say here's a shell script
case case
... <- many lines
esac* <- cursor here
both `blink-matching-open' and `show-paren-mode' emitted "case c";
Now `show-paren-mode' instead emits "case case" if
`show-paren-context-when-offscreen' is t.
> From: Mattias Engdegård
> Subject: Re: Bug?
> Date: Wed, 3 May 2023 14:27:37 +0200
>
>>> Don't we have an existing suitable face to inherit from?
>>
>> Do you mean to inherit from those faces that set colors separately
>> for light and dark backgrounds?
>
> Yes, and it's much easier for the user to customise a single
> "highlight" face than dozens of them. There is a face literally
> named "highlight"; would that do? If so, maybe we don't even need a
> new face at all.
>
> If you really want a new face that uses green text by default,
> something like
>
> (defface blink-matching-paren-offscreen
Thanks. I finally chose the new face that you defined, because
"highlight" is difficult to distinguish against my dark background.
--
shynur
[-- Attachment #2: 0001-Show-paren-mode-highlights-entire-delimiter-in-the-e.patch --]
[-- Type: application/octet-stream, Size: 9464 bytes --]
From 80c8c26876f82c9c8ab20f47b28ded62f0b13990 Mon Sep 17 00:00:00 2001
From: Shynur <one.last.kiss@outlook.com>
Date: Fri, 5 May 2023 04:30:42 +0800
Subject: [PATCH] Show-paren-mode highlights entire delimiter in the echo area
Show-paren-mode now displays the context string containing the entire
matched delimiter and highlights it conditionally.
* lisp/simple.el (blink-matching-paren-offscreen): Set a color for
light background.
(blink-paren-open-paren-line-string): Can return the context string
containing the entire matched delimiter by specifying the value of the
argument DELIMITER-LENGTH.
* lisp/paren.el (show-paren-function): Can highlight the matched
delimiter in the echo area now.
* doc/emacs/programs.texi (Matching Parentheses): Add the description
of `blink-matching-paren-highlight-offscreen'.
; * doc/emacs/files.texi (Visiting Files): Fix typo.
---
doc/emacs/files.texi | 2 +-
doc/emacs/programs.texi | 13 ++++++++++++-
lisp/paren.el | 11 +++++++----
lisp/simple.el | 41 ++++++++++++++++++++++++++++-------------
4 files changed, 48 insertions(+), 19 deletions(-)
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 74315a05bbd..46056b6d4fa 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -232,7 +232,7 @@ Visiting
characters, Emacs visits all the files that match it. (On
case-insensitive filesystems, Emacs matches the wildcards disregarding
the letter case.) Wildcards include @samp{?}, @samp{*}, and
-@samp{[@dots{}]} sequences. To enter the wild card @samp{?} in a file
+@samp{[@dots{}]} sequences. To enter the wildcard @samp{?} in a file
name in the minibuffer, you need to type @kbd{C-q ?}. @xref{Quoted
File Names}, for information on how to visit a file whose name
actually contains wildcard characters. You can disable the wildcard
diff --git a/doc/emacs/programs.texi b/doc/emacs/programs.texi
index 62df88a731e..3ee2a48de08 100644
--- a/doc/emacs/programs.texi
+++ b/doc/emacs/programs.texi
@@ -930,7 +930,8 @@ Matching
@vindex blink-matching-paren
@vindex blink-matching-paren-distance
@vindex blink-matching-delay
- Three variables control the display of matching parentheses:
+@vindex blink-matching-paren-highlight-offscreen
+ Four variables control the display of matching parentheses:
@itemize @bullet
@item
@@ -950,6 +951,16 @@ Matching
back to search to find the matching opening delimiter. If the match
is not found in that distance, Emacs stops scanning and nothing is
displayed. The default is 102400.
+
+@item
+@code{blink-matching-paren-highlight-offscreen} says whether to use
+highlighting to indicate the location of the matched opening delimiter
+when it is off the screen and thus shown in the echo area. The
+default is @code{nil}. Note that only the 1st character of the
+delimiter is highlit; if you want to highlight the entire delimiter
+in the echo area, enable @code{show-paren-mode} (see below) and set
+both this option and @code{show-paren-context-when-offscreen} to
+@code{t}.
@end itemize
@cindex Show Paren mode
diff --git a/lisp/paren.el b/lisp/paren.el
index 4c91fd29490..c03605987d8 100644
--- a/lisp/paren.el
+++ b/lisp/paren.el
@@ -500,15 +500,15 @@ show-paren-function
(move-overlay show-paren--overlay
there-beg there-end (current-buffer)))
;; If `show-paren-context-when-offscreen' is non-nil and
- ;; point is at a closing paren, show the context around the
- ;; opening paren.
+ ;; point is at a closing paren / delimiter, show the
+ ;; context around the opening paren / delimiter.
(let ((openparen (min here-beg there-beg)))
(when (and show-paren-context-when-offscreen
(not (eql show-paren--last-pos (point)))
(< there-beg here-beg)
(not (pos-visible-in-window-p openparen)))
(let ((context (blink-paren-open-paren-line-string
- openparen))
+ openparen (- there-end there-beg)))
(message-log-max nil))
(cond
((and
@@ -518,7 +518,10 @@ show-paren-function
((eq show-paren-context-when-offscreen 'overlay)
(show-paren--show-context-in-overlay context))
(show-paren-context-when-offscreen
- (minibuffer-message "Matches %s" context))))))
+ (minibuffer-message
+ "%s %s"
+ (propertize "Matches" 'face 'shadow)
+ context))))))
(setq show-paren--last-pos (point))
;; Always set the overlay face, since it varies.
(overlay-put show-paren--overlay 'priority show-paren-priority)
diff --git a/lisp/simple.el b/lisp/simple.el
index 58517dd81f9..4ba748c83d6 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -9235,7 +9235,10 @@ blink-matching-paren-highlight-offscreen
:group 'paren-blinking)
(defface blink-matching-paren-offscreen
- '((t :foreground "green"))
+ '((((class color) (background light))
+ :background "yellow")
+ (((class color) (background dark))
+ :foreground "green"))
"Face for showing in the echo area matched open paren that is off-screen.
This face is used only when `blink-matching-paren-highlight-offscreen'
is non-nil."
@@ -9339,14 +9342,25 @@ blink-matching-open
(delete-overlay blink-matching--overlay)))))
((not show-paren-context-when-offscreen)
(minibuffer-message
- "%s%s"
- (propertize "Matches " 'face 'shadow)
+ "%s %s"
+ (propertize "Matches" 'face 'shadow)
(blink-paren-open-paren-line-string blinkpos)))))))
-(defun blink-paren-open-paren-line-string (pos)
+(defun blink-paren-open-paren-line-string (pos &optional delimiter-length)
"Return the line string that contains the openparen at POS.
-Remove the line string's properties but give the openparen a distinct
-face if `blink-matching-paren-highlight-offscreen' is non-nil."
+
+Before returning, the line string's properties are removed,
+and then its substring of DELIMITER-LENGTH characters
+starting from openparen is propertized with a distinct face
+if `blink-matching-paren-highlight-offscreen' is non-nil."
+ ;; If the openparen is essentially the 1st charater of a matched opening
+ ;; delimiter, we may want the string to be returned to contain the
+ ;; entire delimiter. DELIMITER-LENGTH charaters starting from openparen
+ ;; are guaranteed to be contained.
+ ;; By default, it is 1, assuming that what is matched is an openparen
+ ;; instead of a delimiter whose length >= 2.
+ (when (null delimiter-length)
+ (setq delimiter-length 1))
(save-excursion
(goto-char pos)
;; Capture the regions in terms of (beg . end) conses whose
@@ -9358,11 +9372,11 @@ blink-paren-open-paren-line-string
;; Show what precedes the open in its line, if anything.
((save-excursion (skip-chars-backward " \t") (not (bolp)))
(let ((bol (line-beginning-position)))
- (setq regions (list (cons bol (1+ pos)))
+ (setq regions (list (cons bol (+ pos delimiter-length)))
openparen-idx (- pos bol))))
;; Show what follows the open in its line, if anything.
((save-excursion
- (forward-char 1)
+ (forward-char delimiter-length)
(skip-chars-forward " \t")
(not (eolp)))
(setq regions (list (cons pos (line-end-position)))
@@ -9385,9 +9399,9 @@ blink-paren-open-paren-line-string
;; (length "...")
3))
eol))
- (cons pos (1+ pos)))))
+ (cons pos (+ pos delimiter-length)))))
;; There is nothing to show except the char itself.
- (t (setq regions (list (cons pos (1+ pos)))
+ (t (setq regions (list (cons pos (+ pos delimiter-length)))
openparen-idx 0)))
;; Ensure we've font-locked the context region.
(font-lock-ensure (caar regions) (cdar (last regions)))
@@ -9397,20 +9411,21 @@ blink-paren-open-paren-line-string
(buffer-substring (car region) (cdr region)))
regions
"..."))
- (openparen-next-char-idx (1+ openparen-idx)))
+ (highlit-substring-end
+ (+ openparen-idx delimiter-length)))
(setq line-string (substring-no-properties line-string))
(concat
(substring line-string
0 openparen-idx)
(let ((matched-offscreen-openparen
(substring line-string
- openparen-idx openparen-next-char-idx)))
+ openparen-idx highlit-substring-end)))
(if blink-matching-paren-highlight-offscreen
(propertize matched-offscreen-openparen
'face 'blink-matching-paren-offscreen)
matched-offscreen-openparen))
(substring line-string
- openparen-next-char-idx))))))
+ highlit-substring-end))))))
(defvar blink-paren-function 'blink-matching-open
"Function called, if non-nil, whenever a close parenthesis is inserted.
--
2.34.1
^ permalink raw reply related [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-04 20:57 ` Bug? Shynur Xie
@ 2023-05-05 4:41 ` Eli Zaretskii
2023-05-05 16:18 ` Bug? Shynur Xie
2023-05-06 10:44 ` Bug? Mattias Engdegård
1 sibling, 1 reply; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-05 4:41 UTC (permalink / raw)
To: Shynur Xie; +Cc: mattiase, emacs-devel, luangruo
> From: Shynur Xie <one.last.kiss@outlook.com>
> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>, "luangruo@yahoo.com"
> <luangruo@yahoo.com>
> Date: Thu, 4 May 2023 20:57:36 +0000
> msip_labels:
>
> >> I also noticed that when the closing bracket is comprised of
> >> multiple characters, only the first character is high-lit using
> >> that face. For example, in shell-script-mode, when `esac` matches
> >> `case`, only the `c` in `case` is high-lit. Perhaps this new
> >> feature isn't quite finished yet.
> >
> > Shynur, could you please fix this deficiency?
>
> Patch is attached. To highlight the entire matched opening delimiter:
> (show-paren-mode)
> (setq blink-matching-paren-offscreen t
> show-paren-context-when-offscreen t)
Thanks, but I don't think I understand: didn't you tell that the
problem reported above is not a bug, but the expected and long-time
behavior of blink-matching-paren? If so, what exactly does this patch
fix?
> I also changed the function `blink-paren-open-paren-line-string':
> Originally, say here's a shell script
> case case
> ... <- many lines
> esac* <- cursor here
> both `blink-matching-open' and `show-paren-mode' emitted "case c";
> Now `show-paren-mode' instead emits "case case" if
> `show-paren-context-when-offscreen' is t.
This seems to be about show-paren-mode, not about
blink-matching-paren. Those are different, though related, features.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-05 4:41 ` Bug? Eli Zaretskii
@ 2023-05-05 16:18 ` Shynur Xie
0 siblings, 0 replies; 44+ messages in thread
From: Shynur Xie @ 2023-05-05 16:18 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: mattiase@acm.org, emacs-devel@gnu.org
> From: Eli Zaretskii
> Subject: Re: Bug?
> Date: Fri, 05 May 2023 07:41:14 +0300
> To: Shynur Xie
>
> didn't you tell that the problem reported above is not a bug, but
> the expected and long-time behavior of blink-matching-paren?
Yes, it is not a bug to the original author of this function. But now
`show-paren-mode' also uses this function, which leads to a bug, or at
least a counterintuitive behavior:
> From: Mattias Engdegård
> For example, in shell-script-mode, when `esac` matches `case`, only
> the `c` in `case` is high-lit.
_____________________________
Let me explain it in details.
At first (when emacs-version is 28.2), there was only the function
`blink-matching-open'. Later, someone refactored this function, by
separating out a part of it, thus there is a function named
`blink-paren-open-paren-line-string' now.
Both of the above 2 functions are defined in <lisp/simple.el> to
implement the basic parenthesis matching feature (let's call it
`blink-matching` for now) mentioned in:
> (emacs)26.4.3
> Emacs _briefly_indicates_ the location of the matching opening
> delimiter, ... If it is not on the screen, Emacs displays some of
> the text near it in the echo area."
The goal of `blink-matching` is just to _briefly_indicate_ the
location of delimiter (such as '(' in Lisp and 'case' in Bash), so it
is reasonable to _treat_only_the_1st_character_of_a_delimiter_
specially -- `blink-matching` highlights only the 1st character (to
observe this, you need to disable `show-paren-mode' first) when the
matched delimiter is on-screen; when it's off-screen, only the 1st
character is made sure to be contained in the message that is shown in
the echo area. For example, in `shell-script-mode', when off-screen:
case case <- off-screen
^
... <- many empty lines
esac* <- cursor here
only "case c" is shown in the echo area. Thus my first patch can only
highlights "c" because "ase" is not contained at all. So
> From: Mattias Engdegård
> I also noticed that when the closing bracket is comprised of
> multiple characters, only the first character is high-lit using that
> face.
_____________________
> From: Eli Zaretskii
> Shynur, could you please fix this deficiency?
Deficiency, yes, it is, and belongs to `show-paren-mode'.
Let's take a look at what `show-paren-mode' provides first:
> (emacs)26.4.3
> Show Paren mode is a minor mode that provides a _more_powerful_ kind
> of automatic matching.
So this mode treats the entire matched delimiter specially, instead of
only the 1st character. For example, in `shell-script-mode', when
on-screen:
case <- on-screen
^^^^
esac* <- cursor here
the entire "case" is highlit.
But when off-screen, if `show-paren-context-when-offscreen' (an option
of `show-paren-mode') is t, the job of showing the matched off-screen
delimiter in the echo area is taken by `show-paren-mode' instead of
`blink-matching`.
I notice that `show-paren-mode` does this job
_simply_by_invoking_`blink-paren-open-paren-line-string'_, which
assumes that only the 1st character of the matched delimiter needs to
be treated specially -- same example as the first one I mentioned:
case case <- off-screen
^
... <- many empty lines
esac* <- cursor here
"case c" is shown in the area.
> From: Eli Zaretskii
> This seems to be about show-paren-mode, not about
> blink-matching-paren.
About both, IMO. They both use `blink-paren-open-paren-line-string'
but this function only guarantees the returned string containes the
1st character of a delimiter, which is suitable for `blink-matching`
but not for `show-paren-mode'.
_____________________
> From: Eli Zaretskii
> what exactly does this patch fix?
It fixes cases such as "case c". Thus, if
`show-paren-context-when-offscreen' is t, "case case", which contains
the entire matched delimiter -- "case", will be shown in the echo
area. And if `blink-matching-paren-highlight-offscreen' is also t,
"Matches case case"
^^^^
the entire delimiter, instead of only its 1st character, will be
highlit.
--
shynur
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-04 20:57 ` Bug? Shynur Xie
2023-05-05 4:41 ` Bug? Eli Zaretskii
@ 2023-05-06 10:44 ` Mattias Engdegård
2023-05-06 14:58 ` Bug? Shynur Xie
1 sibling, 1 reply; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-06 10:44 UTC (permalink / raw)
To: Shynur Xie; +Cc: Eli Zaretskii, emacs-devel@gnu.org, luangruo@yahoo.com
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
4 maj 2023 kl. 22.57 skrev Shynur Xie <one.last.kiss@outlook.com>:
> I finally chose the new face that you defined, because
> "highlight" is difficult to distinguish against my dark background.
Maybe we should make the `highlight` face better at highlighting then?
On white background it seems to do alright. Comparison, using `highlight`:
It indeed seems that `highlight` on dark background is a bit too timid. What about, say, #006090 instead of darkolivegreen?
[-- Attachment #2.1: Type: text/html, Size: 1256 bytes --]
[-- Attachment #2.2: Skärmavbild 2023-05-06 kl. 12.24.13.png --]
[-- Type: image/png, Size: 9744 bytes --]
[-- Attachment #2.3: Skärmavbild 2023-05-06 kl. 12.24.22.png --]
[-- Type: image/png, Size: 9441 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-06 10:44 ` Bug? Mattias Engdegård
@ 2023-05-06 14:58 ` Shynur Xie
2023-05-06 15:24 ` Bug? Eli Zaretskii
2023-05-07 11:08 ` Bug? Mattias Engdegård
0 siblings, 2 replies; 44+ messages in thread
From: Shynur Xie @ 2023-05-06 14:58 UTC (permalink / raw)
To: Mattias Engdegård; +Cc: Eli Zaretskii, emacs-devel@gnu.org
> From: Mattias Engdegård
> Date: Sat, 6 May 2023 12:44:57 +0200
>
> It indeed seems that `highlight` on dark background is a bit too
> timid. What about, say, #006090 instead of darkolivegreen?
Thanks. But did you notice that all the faces defined in
<lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
I'm a little worried that if we use "#RRGGBB", it might be not
intuitive and not fit with the overall style of <lisp/faces.el>.
If you change the face `highlight`, I'll rewrite my patch to make
`blink-matching-paren-offscreen` inherit from it.
____________________
Eli, if you think my last patch helps, please don't install it yet,
because it defines a new face for `blink-matching-paren-offscreen` and
thus should be rewritten if Mattias changes face `highlight`. Thanks.
By the way,
> From: Eli Zaretskii
> Subject: Re: emacs-29 9b775ddc057 1/2
> Date: Sat, 06 May 2023 16:22:12 +0300
>
> today, I've been at the keyboard, working on various Emacs issues
> for the last 7 hours without any breaks, and this is my weekend!
I appreciate the effort you're putting into resolving those issues,
but it's important to prioritize your own well-being too! Perhaps
taking a break to recharge would be helpful. Wish you all the best.
--
shynur
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-06 14:58 ` Bug? Shynur Xie
@ 2023-05-06 15:24 ` Eli Zaretskii
2023-05-07 11:08 ` Bug? Mattias Engdegård
1 sibling, 0 replies; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-06 15:24 UTC (permalink / raw)
To: Shynur Xie; +Cc: mattiase, emacs-devel
> From: Shynur Xie <one.last.kiss@outlook.com>
> CC: Eli Zaretskii <eliz@gnu.org>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Sat, 6 May 2023 14:58:09 +0000
>
> > today, I've been at the keyboard, working on various Emacs issues
> > for the last 7 hours without any breaks, and this is my weekend!
>
> I appreciate the effort you're putting into resolving those issues,
> but it's important to prioritize your own well-being too! Perhaps
> taking a break to recharge would be helpful. Wish you all the best.
Thanks, but taking a break will just mean I will need to work much
harder when I get back from the break.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-06 14:58 ` Bug? Shynur Xie
2023-05-06 15:24 ` Bug? Eli Zaretskii
@ 2023-05-07 11:08 ` Mattias Engdegård
2023-05-07 12:05 ` Bug? Po Lu
1 sibling, 1 reply; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-07 11:08 UTC (permalink / raw)
To: Shynur Xie; +Cc: Eli Zaretskii, emacs-devel@gnu.org
6 maj 2023 kl. 16.58 skrev Shynur Xie <one.last.kiss@outlook.com>:
> But did you notice that all the faces defined in
> <lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
> I'm a little worried that if we use "#RRGGBB", it might be not
> intuitive and not fit with the overall style of <lisp/faces.el>.
I have no opinion on the matter. I suppose `darkskyblue4` is the closest. Which colour would you prefer?
Or for that matter, what about using the `show-paren-match` face instead? That's what it's there for, isn't it?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 11:08 ` Bug? Mattias Engdegård
@ 2023-05-07 12:05 ` Po Lu
2023-05-07 12:17 ` Bug? Eli Zaretskii
0 siblings, 1 reply; 44+ messages in thread
From: Po Lu @ 2023-05-07 12:05 UTC (permalink / raw)
To: Mattias Engdegård; +Cc: Shynur Xie, Eli Zaretskii, emacs-devel@gnu.org
Mattias Engdegård <mattiase@acm.org> writes:
> 6 maj 2023 kl. 16.58 skrev Shynur Xie <one.last.kiss@outlook.com>:
>
>> But did you notice that all the faces defined in
>> <lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
>> I'm a little worried that if we use "#RRGGBB", it might be not
>> intuitive and not fit with the overall style of <lisp/faces.el>.
>
> I have no opinion on the matter. I suppose `darkskyblue4` is the
> closest. Which colour would you prefer?
Please try very hard to avoid using device or intensity specifications
for colors. This is because many vendors of X servers perform color
calibration for graphics devices by editing the list of pre-defined X
colors.
In addition, using non-predefined colors means that you will be more
likely to allocate a color cell in the default colormap which no other
program can use. While not as important as it used to be, excessive
color use is still something to keep in mind when writing programs.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 12:05 ` Bug? Po Lu
@ 2023-05-07 12:17 ` Eli Zaretskii
2023-05-07 12:54 ` Bug? Po Lu
2023-05-07 13:36 ` Bug? Shynur Xie
0 siblings, 2 replies; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-07 12:17 UTC (permalink / raw)
To: Po Lu; +Cc: mattiase, one.last.kiss, emacs-devel
> From: Po Lu <luangruo@yahoo.com>
> Cc: Shynur Xie <one.last.kiss@outlook.com>, Eli Zaretskii <eliz@gnu.org>,
> "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Sun, 07 May 2023 20:05:33 +0800
>
> Mattias Engdegård <mattiase@acm.org> writes:
>
> > 6 maj 2023 kl. 16.58 skrev Shynur Xie <one.last.kiss@outlook.com>:
> >
> >> But did you notice that all the faces defined in
> >> <lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
> >> I'm a little worried that if we use "#RRGGBB", it might be not
> >> intuitive and not fit with the overall style of <lisp/faces.el>.
> >
> > I have no opinion on the matter. I suppose `darkskyblue4` is the
> > closest. Which colour would you prefer?
>
> Please try very hard to avoid using device or intensity specifications
> for colors. This is because many vendors of X servers perform color
> calibration for graphics devices by editing the list of pre-defined X
> colors.
>
> In addition, using non-predefined colors means that you will be more
> likely to allocate a color cell in the default colormap which no other
> program can use. While not as important as it used to be, excessive
> color use is still something to keep in mind when writing programs.
Personally, I fail to understand why we are considering changes in
default faces for this minor issue. We have enough faces from which
to inherit, faces whose definitions endured many years of use and
scrutiny. Let's not over-engineer, OK?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 12:17 ` Bug? Eli Zaretskii
@ 2023-05-07 12:54 ` Po Lu
2023-05-07 13:36 ` Bug? Shynur Xie
1 sibling, 0 replies; 44+ messages in thread
From: Po Lu @ 2023-05-07 12:54 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: mattiase, one.last.kiss, emacs-devel
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: Shynur Xie <one.last.kiss@outlook.com>, Eli Zaretskii <eliz@gnu.org>,
>> "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> Date: Sun, 07 May 2023 20:05:33 +0800
>>
>> Mattias Engdegård <mattiase@acm.org> writes:
>>
>> > 6 maj 2023 kl. 16.58 skrev Shynur Xie <one.last.kiss@outlook.com>:
>> >
>> >> But did you notice that all the faces defined in
>> >> <lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
>> >> I'm a little worried that if we use "#RRGGBB", it might be not
>> >> intuitive and not fit with the overall style of <lisp/faces.el>.
>> >
>> > I have no opinion on the matter. I suppose `darkskyblue4` is the
>> > closest. Which colour would you prefer?
>>
>> Please try very hard to avoid using device or intensity specifications
>> for colors. This is because many vendors of X servers perform color
>> calibration for graphics devices by editing the list of pre-defined X
>> colors.
>>
>> In addition, using non-predefined colors means that you will be more
>> likely to allocate a color cell in the default colormap which no other
>> program can use. While not as important as it used to be, excessive
>> color use is still something to keep in mind when writing programs.
>
> Personally, I fail to understand why we are considering changes in
> default faces for this minor issue. We have enough faces from which
> to inherit, faces whose definitions endured many years of use and
> scrutiny. Let's not over-engineer, OK?
I thought the discussion was about introducing a new face, this time
with a dangerous color.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 12:17 ` Bug? Eli Zaretskii
2023-05-07 12:54 ` Bug? Po Lu
@ 2023-05-07 13:36 ` Shynur Xie
2023-05-07 13:51 ` Bug? Mattias Engdegård
1 sibling, 1 reply; 44+ messages in thread
From: Shynur Xie @ 2023-05-07 13:36 UTC (permalink / raw)
To: Eli Zaretskii, Mattias Engdegård; +Cc: emacs-devel@gnu.org, Po Lu
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
> From: Eli Zaretskii
> Date: Sun, 07 May 2023 15:17:24 +0300
>
> Personally, I fail to understand why we are considering changes in
> default faces for this minor issue.
Let me briefly summarize the discussion between Mattias and me, to
save your time.
`blink-matching-paren-offscreen` has its own face defined by me, then
Mattias suggested a color for it when background is light, or just
inheriting from `highlight`. I finally chose to use the suggested
color and wrote it into my new patch. (The primary goal of this patch
is to fix the deficiency mentioned by Mattias.)
The rest of the discussion about `highlight` was just as you said:
> Let's not over-engineer, OK?
Okay, stop talking about these faces.
Mattias, let's put the discussion about faces aside now, and focus on
the problem you mentioned -- only "case c" is shown in the echo area
and only "c" is highlit, OK? And feel free to change the face
`blink-matching-paren-offscreen` after this problem is solved.
Again, I attached that patch here. Any opinion?
--
shynur
[-- Attachment #2: 0001-Show-paren-mode-highlights-entire-delimiter-in-the-e.patch --]
[-- Type: application/octet-stream, Size: 9464 bytes --]
From 80c8c26876f82c9c8ab20f47b28ded62f0b13990 Mon Sep 17 00:00:00 2001
From: Shynur <one.last.kiss@outlook.com>
Date: Fri, 5 May 2023 04:30:42 +0800
Subject: [PATCH] Show-paren-mode highlights entire delimiter in the echo area
Show-paren-mode now displays the context string containing the entire
matched delimiter and highlights it conditionally.
* lisp/simple.el (blink-matching-paren-offscreen): Set a color for
light background.
(blink-paren-open-paren-line-string): Can return the context string
containing the entire matched delimiter by specifying the value of the
argument DELIMITER-LENGTH.
* lisp/paren.el (show-paren-function): Can highlight the matched
delimiter in the echo area now.
* doc/emacs/programs.texi (Matching Parentheses): Add the description
of `blink-matching-paren-highlight-offscreen'.
; * doc/emacs/files.texi (Visiting Files): Fix typo.
---
doc/emacs/files.texi | 2 +-
doc/emacs/programs.texi | 13 ++++++++++++-
lisp/paren.el | 11 +++++++----
lisp/simple.el | 41 ++++++++++++++++++++++++++++-------------
4 files changed, 48 insertions(+), 19 deletions(-)
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 74315a05bbd..46056b6d4fa 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -232,7 +232,7 @@ Visiting
characters, Emacs visits all the files that match it. (On
case-insensitive filesystems, Emacs matches the wildcards disregarding
the letter case.) Wildcards include @samp{?}, @samp{*}, and
-@samp{[@dots{}]} sequences. To enter the wild card @samp{?} in a file
+@samp{[@dots{}]} sequences. To enter the wildcard @samp{?} in a file
name in the minibuffer, you need to type @kbd{C-q ?}. @xref{Quoted
File Names}, for information on how to visit a file whose name
actually contains wildcard characters. You can disable the wildcard
diff --git a/doc/emacs/programs.texi b/doc/emacs/programs.texi
index 62df88a731e..3ee2a48de08 100644
--- a/doc/emacs/programs.texi
+++ b/doc/emacs/programs.texi
@@ -930,7 +930,8 @@ Matching
@vindex blink-matching-paren
@vindex blink-matching-paren-distance
@vindex blink-matching-delay
- Three variables control the display of matching parentheses:
+@vindex blink-matching-paren-highlight-offscreen
+ Four variables control the display of matching parentheses:
@itemize @bullet
@item
@@ -950,6 +951,16 @@ Matching
back to search to find the matching opening delimiter. If the match
is not found in that distance, Emacs stops scanning and nothing is
displayed. The default is 102400.
+
+@item
+@code{blink-matching-paren-highlight-offscreen} says whether to use
+highlighting to indicate the location of the matched opening delimiter
+when it is off the screen and thus shown in the echo area. The
+default is @code{nil}. Note that only the 1st character of the
+delimiter is highlit; if you want to highlight the entire delimiter
+in the echo area, enable @code{show-paren-mode} (see below) and set
+both this option and @code{show-paren-context-when-offscreen} to
+@code{t}.
@end itemize
@cindex Show Paren mode
diff --git a/lisp/paren.el b/lisp/paren.el
index 4c91fd29490..c03605987d8 100644
--- a/lisp/paren.el
+++ b/lisp/paren.el
@@ -500,15 +500,15 @@ show-paren-function
(move-overlay show-paren--overlay
there-beg there-end (current-buffer)))
;; If `show-paren-context-when-offscreen' is non-nil and
- ;; point is at a closing paren, show the context around the
- ;; opening paren.
+ ;; point is at a closing paren / delimiter, show the
+ ;; context around the opening paren / delimiter.
(let ((openparen (min here-beg there-beg)))
(when (and show-paren-context-when-offscreen
(not (eql show-paren--last-pos (point)))
(< there-beg here-beg)
(not (pos-visible-in-window-p openparen)))
(let ((context (blink-paren-open-paren-line-string
- openparen))
+ openparen (- there-end there-beg)))
(message-log-max nil))
(cond
((and
@@ -518,7 +518,10 @@ show-paren-function
((eq show-paren-context-when-offscreen 'overlay)
(show-paren--show-context-in-overlay context))
(show-paren-context-when-offscreen
- (minibuffer-message "Matches %s" context))))))
+ (minibuffer-message
+ "%s %s"
+ (propertize "Matches" 'face 'shadow)
+ context))))))
(setq show-paren--last-pos (point))
;; Always set the overlay face, since it varies.
(overlay-put show-paren--overlay 'priority show-paren-priority)
diff --git a/lisp/simple.el b/lisp/simple.el
index 58517dd81f9..4ba748c83d6 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -9235,7 +9235,10 @@ blink-matching-paren-highlight-offscreen
:group 'paren-blinking)
(defface blink-matching-paren-offscreen
- '((t :foreground "green"))
+ '((((class color) (background light))
+ :background "yellow")
+ (((class color) (background dark))
+ :foreground "green"))
"Face for showing in the echo area matched open paren that is off-screen.
This face is used only when `blink-matching-paren-highlight-offscreen'
is non-nil."
@@ -9339,14 +9342,25 @@ blink-matching-open
(delete-overlay blink-matching--overlay)))))
((not show-paren-context-when-offscreen)
(minibuffer-message
- "%s%s"
- (propertize "Matches " 'face 'shadow)
+ "%s %s"
+ (propertize "Matches" 'face 'shadow)
(blink-paren-open-paren-line-string blinkpos)))))))
-(defun blink-paren-open-paren-line-string (pos)
+(defun blink-paren-open-paren-line-string (pos &optional delimiter-length)
"Return the line string that contains the openparen at POS.
-Remove the line string's properties but give the openparen a distinct
-face if `blink-matching-paren-highlight-offscreen' is non-nil."
+
+Before returning, the line string's properties are removed,
+and then its substring of DELIMITER-LENGTH characters
+starting from openparen is propertized with a distinct face
+if `blink-matching-paren-highlight-offscreen' is non-nil."
+ ;; If the openparen is essentially the 1st charater of a matched opening
+ ;; delimiter, we may want the string to be returned to contain the
+ ;; entire delimiter. DELIMITER-LENGTH charaters starting from openparen
+ ;; are guaranteed to be contained.
+ ;; By default, it is 1, assuming that what is matched is an openparen
+ ;; instead of a delimiter whose length >= 2.
+ (when (null delimiter-length)
+ (setq delimiter-length 1))
(save-excursion
(goto-char pos)
;; Capture the regions in terms of (beg . end) conses whose
@@ -9358,11 +9372,11 @@ blink-paren-open-paren-line-string
;; Show what precedes the open in its line, if anything.
((save-excursion (skip-chars-backward " \t") (not (bolp)))
(let ((bol (line-beginning-position)))
- (setq regions (list (cons bol (1+ pos)))
+ (setq regions (list (cons bol (+ pos delimiter-length)))
openparen-idx (- pos bol))))
;; Show what follows the open in its line, if anything.
((save-excursion
- (forward-char 1)
+ (forward-char delimiter-length)
(skip-chars-forward " \t")
(not (eolp)))
(setq regions (list (cons pos (line-end-position)))
@@ -9385,9 +9399,9 @@ blink-paren-open-paren-line-string
;; (length "...")
3))
eol))
- (cons pos (1+ pos)))))
+ (cons pos (+ pos delimiter-length)))))
;; There is nothing to show except the char itself.
- (t (setq regions (list (cons pos (1+ pos)))
+ (t (setq regions (list (cons pos (+ pos delimiter-length)))
openparen-idx 0)))
;; Ensure we've font-locked the context region.
(font-lock-ensure (caar regions) (cdar (last regions)))
@@ -9397,20 +9411,21 @@ blink-paren-open-paren-line-string
(buffer-substring (car region) (cdr region)))
regions
"..."))
- (openparen-next-char-idx (1+ openparen-idx)))
+ (highlit-substring-end
+ (+ openparen-idx delimiter-length)))
(setq line-string (substring-no-properties line-string))
(concat
(substring line-string
0 openparen-idx)
(let ((matched-offscreen-openparen
(substring line-string
- openparen-idx openparen-next-char-idx)))
+ openparen-idx highlit-substring-end)))
(if blink-matching-paren-highlight-offscreen
(propertize matched-offscreen-openparen
'face 'blink-matching-paren-offscreen)
matched-offscreen-openparen))
(substring line-string
- openparen-next-char-idx))))))
+ highlit-substring-end))))))
(defvar blink-paren-function 'blink-matching-open
"Function called, if non-nil, whenever a close parenthesis is inserted.
--
2.34.1
^ permalink raw reply related [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 13:36 ` Bug? Shynur Xie
@ 2023-05-07 13:51 ` Mattias Engdegård
2023-05-07 14:42 ` Bug? Shynur Xie
0 siblings, 1 reply; 44+ messages in thread
From: Mattias Engdegård @ 2023-05-07 13:51 UTC (permalink / raw)
To: Shynur Xie; +Cc: Eli Zaretskii, emacs-devel@gnu.org, Po Lu
7 maj 2023 kl. 15.36 skrev Shynur Xie <one.last.kiss@outlook.com>:
> Again, I attached that patch here. Any opinion?
Did you consider using the face `show-paren-match` instead? It seems fine on dark background, too.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 13:51 ` Bug? Mattias Engdegård
@ 2023-05-07 14:42 ` Shynur Xie
2023-05-07 15:06 ` Bug? Eli Zaretskii
0 siblings, 1 reply; 44+ messages in thread
From: Shynur Xie @ 2023-05-07 14:42 UTC (permalink / raw)
To: Mattias Engdegård, Eli Zaretskii; +Cc: emacs-devel@gnu.org
> From: Mattias Engdegård
> Date: Sun, 7 May 2023 15:51:39 +0200
>
> Did you consider using the face `show-paren-match` instead? It seems
> fine on dark background, too.
It is a good choice, and
> From: Shynur
> feel free to change the face `blink-matching-paren-offscreen` after
> this problem is solved.
______________
> From: Shynur
> Again, I attached that patch here. Any opinion?
Eli, we've talked a lot about that patch and what it fixes. In case
you forget our conversations, I listed them here:
Mattias:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00030.html>
Me:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00100.html>
You:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00109.html>
Me:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00144.html>
--
shynur
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Bug?
2023-05-07 14:42 ` Bug? Shynur Xie
@ 2023-05-07 15:06 ` Eli Zaretskii
0 siblings, 0 replies; 44+ messages in thread
From: Eli Zaretskii @ 2023-05-07 15:06 UTC (permalink / raw)
To: Shynur Xie; +Cc: mattiase, emacs-devel
> From: Shynur Xie <one.last.kiss@outlook.com>
> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Sun, 7 May 2023 14:42:50 +0000
>
> Eli, we've talked a lot about that patch and what it fixes. In case
> you forget our conversations, I listed them here:
>
> Mattias:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00030.html>
> Me:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00100.html>
> You:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00109.html>
> Me:<lists.gnu.org/archive/html/emacs-devel/2023-05/msg00144.html>
I'll get to that eventually.
^ permalink raw reply [flat|nested] 44+ messages in thread
end of thread, other threads:[~2023-05-07 15:06 UTC | newest]
Thread overview: 44+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <875y9aciir.fsf.ref@yahoo.com>
2023-05-03 1:26 ` Bug? Po Lu
2023-05-03 9:40 ` Bug? Mattias Engdegård
2023-05-03 10:12 ` Bug? Mattias Engdegård
2023-05-03 11:24 ` Bug? Shynur Xie
2023-05-03 12:27 ` Bug? Mattias Engdegård
2023-05-03 17:22 ` Bug? Juri Linkov
2023-05-03 11:24 ` Bug? Eli Zaretskii
2023-05-03 11:26 ` Bug? Shynur Xie
2023-05-04 8:35 ` Bug? Shynur Xie
2023-05-04 20:57 ` Bug? Shynur Xie
2023-05-05 4:41 ` Bug? Eli Zaretskii
2023-05-05 16:18 ` Bug? Shynur Xie
2023-05-06 10:44 ` Bug? Mattias Engdegård
2023-05-06 14:58 ` Bug? Shynur Xie
2023-05-06 15:24 ` Bug? Eli Zaretskii
2023-05-07 11:08 ` Bug? Mattias Engdegård
2023-05-07 12:05 ` Bug? Po Lu
2023-05-07 12:17 ` Bug? Eli Zaretskii
2023-05-07 12:54 ` Bug? Po Lu
2023-05-07 13:36 ` Bug? Shynur Xie
2023-05-07 13:51 ` Bug? Mattias Engdegård
2023-05-07 14:42 ` Bug? Shynur Xie
2023-05-07 15:06 ` Bug? Eli Zaretskii
2023-05-03 11:23 ` Bug? Eli Zaretskii
2017-06-20 13:38 bug? John Kitchin
2017-06-29 14:36 ` bug? Nicolas Goaziou
2017-06-30 0:53 ` bug? John Kitchin
2017-07-01 12:30 ` bug? Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 14:47 Bug?? Susan Cragin
2014-05-06 15:28 ` Bug?? Maurice
2014-05-06 21:30 ` Bug?? Suvayu Ali
2014-05-07 16:15 ` Bug?? Achim Gratz
2014-02-06 10:15 Bug: "#+STARTUP: content" shows text as well as headlines [8.2.5h (8.2.5h-elpa @ ~/.emacs.d/elpa/org/) Paul Stansell
2014-02-06 10:42 ` Bastien
2014-02-06 11:38 ` Bastien
2014-03-06 17:32 ` Bug: Paul Stansell
2012-12-04 16:53 Bug? Charles
2012-12-04 19:12 ` Bug? Achim Gratz
2012-12-05 1:20 ` Bug? Charles
2010-05-12 12:50 bug? J. David Boyd
2010-05-12 13:35 ` bug? Bernt Hansen
2010-05-12 14:32 ` bug? J. David Boyd
2005-03-07 16:35 bug ? fg
2003-09-23 11:07 Bug? Mark Espinoza
2002-08-28 17:41 Bug? Sharon A Watkins
2002-08-29 1:38 ` Bug? Juanma Barranquero
2002-08-29 4:44 ` Bug? Eli Zaretskii
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.