From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Can't make org-install.el
Date: Sat, 19 May 2012 14:00:16 +0200 [thread overview]
Message-ID: <87obpkxtwv.fsf@Rainer.invalid> (raw)
In-Reply-To: 80d360qwom.fsf@somewhere.org
Sebastien Vauban writes:
> drwxr-xr-x+ 1 Seb Aucun 0 May 19 12:30 lisp
: ^
:__________/
This tells you that in addition to the Cygwin permissions Windows ACL
are in effect. These may partially or completely subvert the POSIX
permissions. Since you've re-created the directory, these ACL are most
likely inherited ACL (applied from directories further up in the
hierarchy).
> Would it be possible to have a more detailed reporting of the problem? For
> example, I don't understand why org-install.el should be read-only, while
> there was none before making autoloads... So, such a buffer has been
> created... but can't be saved?
Me neither and I've been using that same setup at work for months
without any such problems. Only org-install.el seems to be read-only
however, while org-version.el (which is created by the same method) is
not, which makes this even more puzzling... But here's one other oddity
in your log which may be able to explain it:
> Loading vc-svn...
It looks like lisp (or all of org probably) is both under SVN and Git
version control... That is a Bad Idea™ and might explain why the buffer
becomes read-only if org-install.el is already registered in SVN (which
doesn't allow non-check-out files to be edited). So can you please
remove the Git work tree completely from SVN or just install in a
pristine location?
> Other question: why do we have to make org-install.el? Shouldn't it be
> distributed with the other files, without requiring all users to make it?
Because you use the sources and have to generate all the things that
need to be generated. The generated files might be included in
distribution archives, Bastien and I are currently thinking about that.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-05-19 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 20:49 Can't make org-install.el Sebastien Vauban
2012-05-19 8:54 ` Achim Gratz
2012-05-19 10:42 ` Sebastien Vauban
2012-05-19 12:00 ` Achim Gratz [this message]
2012-05-19 13:40 ` Sebastien Vauban
2012-05-19 15:11 ` Achim Gratz
2012-05-19 17:56 ` [PATCH] " Achim Gratz
2012-05-19 18:05 ` Bastien
2012-05-19 19:00 ` Sebastien Vauban
2012-05-19 19:17 ` Achim Gratz
2012-05-19 19:41 ` Achim Gratz
2012-05-19 20:27 ` Achim Gratz
2012-05-21 8:37 ` Sebastien Vauban
2012-05-21 8:59 ` Sebastien Vauban
2012-05-23 22:01 ` Achim Gratz
2012-05-21 13:34 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obpkxtwv.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).