From: Elliott Slaughter <elliottslaughter@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Symbol's value as variable is void: org-src-lang-modes
Date: Tue, 15 Aug 2017 12:34:21 -0700 [thread overview]
Message-ID: <CAJ9X=kaMTmczFu8KZzLh6if1v0+nKD6sXgh6M8vzAf3W7FBWqA@mail.gmail.com> (raw)
In-Reply-To: <CAJ9X=kZcg1tDe1P_ZHkMf=kwRQkL9QtMHT63t9XW17C9z31gNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
Actually, the backtrace goes through the el-get loaddefs file, so maybe
something is going wrong there. Let me check with the el-get developers and
see if they know what is going on.
On Tue, Aug 15, 2017 at 12:27 PM, Elliott Slaughter <
elliottslaughter@gmail.com> wrote:
> When I install a fresh copy of org-mode via el-get, I see the following
> error:
>
> Bug: Symbol's value as variable is void: org-src-lang-modes
>
> I don't believe this is a problem in el-get, but if I'm wrong, let me know
> and I will take this up with the el-get developers.
>
> Here is the backtrace:
>
> Debugger entered--Lisp error: (void-variable org-src-lang-modes)
> add-to-list(org-src-lang-modes ("sclang" . sclang))
> byte-code("\300\301\302\303\304\"\"\207" [with-eval-after-load "org"
> add-to-list org-src-lang-modes ("sclang" . sclang)] 5)
> load("/home/eslaught/.emacs.d/el-get/.loaddefs" nil t)
> el-get-load-fast("/home/eslaught/.emacs.d/el-get/.loaddefs.el")
> el-get-eval-autoloads()
> el-get(sync)
> econf-install()
> eval-buffer(#<buffer *load*-610652> nil "/home/eslaught/econf/econf-helper.el"
> nil t) ; Reading at buffer position 1907
> load-with-code-conversion("/home/eslaught/econf/econf-helper.el"
> "/home/eslaught/econf/econf-helper.el" nil t)
> require(econf-helper)
> eval-buffer(#<buffer *load*> nil "/home/eslaught/.emacs" nil t) ;
> Reading at buffer position 205
> load-with-code-conversion("/home/eslaught/.emacs"
> "/home/eslaught/.emacs" t t)
> load("~/.emacs" t t)
> #[0 "^H\205\262^@ \306=\203^Q^@\307^H\310Q\202;^@
> \311=\204^^^@\307^H\312Q\202;^@\313\307\314\315#\203*^@\316\
> 202;^@\313\307\314\317#$
> command-line()
> normal-top-level()
>
> Emacs : GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7)
> of 2014-03-07 on lamiak, modified by Debian
> Package: Org mode installed via el-get, from the following Git commit
>
> commit 489080124210a78d6622c79ede5c003e07c2ccb8
> Merge: b900a85 731f59f
> Author: Kyle Meyer <kyle@kyleam.com>
> Date: Mon Aug 14 22:04:35 2017 -0400
>
> Merge branch 'maint'
>
>
--
Elliott Slaughter
"Don't worry about what anybody else is going to do. The best way to
predict the future is to invent it." - Alan Kay
[-- Attachment #2: Type: text/html, Size: 3087 bytes --]
next prev parent reply other threads:[~2017-08-15 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 19:27 Bug: Symbol's value as variable is void: org-src-lang-modes Elliott Slaughter
2017-08-15 19:34 ` Elliott Slaughter [this message]
2017-08-15 20:10 ` Kaushal Modi
2017-09-07 17:37 ` Elliott Slaughter
2017-09-07 18:27 ` Kaushal Modi
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='CAJ9X=kaMTmczFu8KZzLh6if1v0+nKD6sXgh6M8vzAf3W7FBWqA@mail.gmail.com' \
--to=elliottslaughter@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).