From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to build the C language environment in Emacs?
Date: Sat, 03 Jan 2015 18:48:14 +0100 [thread overview]
Message-ID: <87sifrwyap.fsf@debian.uxu> (raw)
In-Reply-To: mailman.17149.1420274187.1147.help-gnu-emacs@gnu.org
Liu Shengyu<suzylau@kaist.ac.kr> writes:
> Dear I have learned Emacs for a few days by myself.
> And I have been read some books about simply uses of
> Emacs. But I have some questions about how to use it
> practically. My computer is not MAC, and my system
> is Windows 7.
>
> 1. I have been installed MinGW in my computer, and I
> have been checked in MSDOS, and also have been set
> envionment variables in PATH. But I still can't
> compile C file. Emacs tells that gcc is not a
> internal or external command. I think maybe I need
> to write some commands in ~.emacs to combine GCC and
> Emacs, but i don't know to do it. So can you help me
> about this question?
C. GCC. Emacs, ... Windows 7?!
Better to switch to a real OS. Especially if you are
into C.
Then you need a Makefile, and some source. Run
`compile' when you are done.
Some things I found useful:
(setq compilation-scroll-output t)
(setq compilation-mode-hook 'visual-line-mode)
(setq compile-command "make -j 4 -s -k")
(setq compilation-read-command nil) ; use `compile-command'
That's all there is to it.
> 2. I wanna compile (+ #c(0 1.0) 2) But Emacs tells me
> that Debugger entered--Lisp error:
> (invalid-read-syntax "#") Why this simply syntax # is
> not a built-in syntax in my Emacs. How to solve this
> kind of problem?
What do you want to do? Add two to a complex number?
The #c(0 1.0) is used in Common Lisp: it doesn't work
in Elisp. I can't help you, but probably Emacs Calc
can do it; perhaps there you can learn how to use it
in Elisp code.
--
underground experts united
next prev parent reply other threads:[~2015-01-03 17:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17149.1420274187.1147.help-gnu-emacs@gnu.org>
2015-01-03 8:45 ` How to build the C language environment in Emacs? Pascal J. Bourguignon
2015-01-03 17:48 ` Emanuel Berg [this message]
[not found] <mailman.17437.1420670116.1147.help-gnu-emacs@gnu.org>
2015-01-07 22:59 ` Pascal J. Bourguignon
2015-01-08 10:23 ` Nicolas Richard
2015-01-03 4:34 Liu Shengyu
2015-01-03 9:04 ` Quanyang Liu
2015-01-03 14:50 ` Grant Rettke
2015-01-06 19:08 ` Ken Goldman
2015-01-03 15:19 ` Filipp Gunbin
2015-01-09 19:21 ` Oleksandr Gavenko
2015-01-03 17:08 ` Óscar Fuentes
2015-01-06 19:05 ` Ken Goldman
[not found] ` <mailman.17367.1420571149.1147.help-gnu-emacs@gnu.org>
2015-01-07 1:41 ` Emanuel Berg
2015-01-07 2:21 ` Quanyang Liu
2015-01-07 4:35 ` Óscar Fuentes
[not found] ` <mailman.17392.1420605430.1147.help-gnu-emacs@gnu.org>
2015-01-07 4:55 ` Emanuel Berg
2015-01-07 14:16 ` Óscar Fuentes
[not found] ` <mailman.17407.1420640515.1147.help-gnu-emacs@gnu.org>
2015-01-07 15:53 ` Will Parsons
2015-01-07 17:48 ` Rusi
2015-01-07 18:08 ` Óscar Fuentes
2015-01-07 18:12 ` Eli Zaretskii
[not found] ` <mailman.17388.1420597359.1147.help-gnu-emacs@gnu.org>
2015-01-07 3:36 ` Emanuel Berg
2015-01-07 19:37 ` Bob Proulx
2015-01-07 19:58 ` Marcin Borkowski
2015-01-08 2:36 ` Eric Abrahamsen
2015-01-07 22:34 ` Robert Thorpe
2015-01-07 19:01 ` Ken Goldman
2015-01-03 11:10 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sifrwyap.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).