How to build the C language environment in Emacs?

How to build the C language environment in Emacs?

[Liu Shengyu]

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?


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?


Best wishes.
Thanks for your attention.


Suzy Lau

Re: How to build the C language environment in Emacs?

[Quanyang Liu]

On Sat, Jan 03 2015 at 12:34:59 +0800, Liu Shengyu wrote:
> 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.
>

well...IIRC, using Emacs in windows is terrible...


>
> 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?

In fact, maybe you can try to use the full path to your compiler. If it
works, then you can make an alias.

> 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?

The built-in lisp in Emacs is elisp...

Re: How to build the C language environment in Emacs?

[Grant Rettke]

Easiest thing to do is to install Vagrant and boot up a Linux box
there to get Emacs and a C compiler.

On Sat, Jan 3, 2015 at 3:04 AM, Quanyang Liu <lqymgt@gmail.com> wrote:
> On Sat, Jan 03 2015 at 12:34:59 +0800, Liu Shengyu wrote:
>> 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.
>>
>
> well...IIRC, using Emacs in windows is terrible...
>
>
>>
>> 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?
>
> In fact, maybe you can try to use the full path to your compiler. If it
> works, then you can make an alias.
>
>> 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?
>
> The built-in lisp in Emacs is elisp...
>
>



-- 
Grant Rettke
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson

Re: How to build the C language environment in Emacs?

[Ken Goldman]

On 1/3/2015 9:50 AM, Grant Rettke wrote:
> Easiest thing to do is to install Vagrant and boot up a Linux box
> there to get Emacs and a C compiler.

You think that's easier than adding gcc to his PATH environment variable?

Re: How to build the C language environment in Emacs?

[Filipp Gunbin]

On 03/01/2015 12:04 +0300, Quanyang Liu wrote:

> On Sat, Jan 03 2015 at 12:34:59 +0800, Liu Shengyu wrote:
>
> well...IIRC, using Emacs in windows is terrible...

Very usable on Cygwin.  I've worked in it for years.

Filipp

Re: How to build the C language environment in Emacs?

[Oleksandr Gavenko]

On 2015-01-03, Filipp Gunbin wrote:

>> On Sat, Jan 03 2015 at 12:34:59 +0800, Liu Shengyu wrote:
>>
>> well...IIRC, using Emacs in windows is terrible...
>
> Very usable on Cygwin.  I've worked in it for years.

I ever use native Emacs with 'cygwin-mount!!

Because I used to use MS VS toolchain and Cygwin Emacs can't understand
Windows path at all...

See my http://sourceforge.net/u/gavenkoa/dot-emacs/ci/default/tree/.emacs-my

Here some tricks (may be outdated, I sat at Windows host last time 3 year ago)
which integrate native Emacs and Cygwin:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(message "shell, bash, Cygwin, MSYS")

(defvar my-use-windows-shell nil
  "If t 'cmdproxy.exe' will be used as shell. Affect on M-x shell like
  commands. If nil, 'sh' will be used." )

(defun follow-cygwin-symlink ()
  "Follow new-style (and also UCS-16) Cygwin symlinks."
  (save-excursion
    (goto-char 0)
    (when (looking-at "!<symlink>\xff\xfe")
      (find-alternate-file
       (substring
        (decode-coding-string
         (buffer-substring (match-end 0) (point-max))
         'utf-16-le)
        0 -1)                           ; -1 for stripping final \0.
       ))))

(defun my-dos2cygwin-path (path)
  "Convert DOS path to Cygwin according to current mount table."
  (interactive (list (read-directory-name "Enter DOS path: ")))
  (setq path (replace-regexp-in-string "\\\\" "/" (expand-file-name path)))
  (let ( (table cygwin-mount-table--internal) item prefix )
    (while table
      (setq item (car table))
      (setq prefix (concat "\\`" (regexp-quote (car item))))
      (setq table (cdr table))
      (when (string-match prefix path)
        (setq path (replace-regexp-in-string prefix (cdr item) path))
        (setq table nil)
        ) )
    path
    ))

(when (eq system-type 'windows-nt)
  (ignore-errors
    (require 'cygwin-mount)
    (cygwin-mount-activate)
    )
  (add-hook 'find-file-hook 'follow-cygwin-symlink)
  ;; Workaround for Cygwin shell, when set 'CYGWIN=noglob'. By default 'shell-quote-argument'
  ;; quoted by double '\' chars this cause failure.
  (defun shell-quote-argument (argument)
    (concat "'" argument "'")
    )
  ;; Workaround for Cygwin when 'shell-file-name' is 'bash'.
  (setq null-device "/dev/null")
  ;; Use shell from Cygwin/MinGW.
  (setq shell-file-name "bash")
  (setenv "SHELL" "/bin/bash")
  (modify-coding-system-alist 'process "bash" '(cp1251-unix . cp1251-unix))
  )

(when (eq window-system 'w32)
  ;; Fix 'starttls.el' on native Windows Emacs with gnutls-cli from Cygwin.
  ;; 'gnutls-cli' run with '-s' opt and process wait for SIGALRM.
  ;; But build-in native Emacs 'kill' command can not send such Cygwin
  ;; specific sygnal. So 'starttls-negotiate-gnutls' function infinitely
  ;; wait for 'gnutls-cli' output.
  (defadvice signal-process (around cygwin (process sigcode))
    "Use 'kill.exe' instead build-in Emacs 'kill'."
    (if (eq sigcode 'SIGALRM)
        (shell-command
         (format "kill.exe -s SIGALRM %d"
                 (if (processp process) (process-id process) process)))
      ad-do-it
      ))
  (ad-activate 'signal-process)
  (modify-coding-system-alist 'process "gnutls-cli" '(binary . binary))
  )

(when (eq window-system 'w32)
  (add-to-list 'exec-suffixes ".py")
  (add-to-list 'exec-suffixes ".sh")
  (defun executable-find (command) (locate-file command exec-path exec-suffixes))
  )

(ansi-color-for-comint-mode-on)

(setq explicit-bash-args '("-i"))
(setq explicit-sh-args '("-i"))

(if (memq system-type '(windows-nt cygwin))
    (setq ls-lisp-verbosity nil)
  (setq  ls-lisp-verbosity '(links uid gid)))

(when (featurep 'cygwin-mount)
  (setenv "INFOPATH" "/usr/share/info/:~/usr/share/info/:")
  ;; Redefine path-separator to UNIX to update Info-directory-list.
  (let ( (path-separator ":") )
    (require 'info)
    (info-initialize)
    ))

;; Assume that cygwin-mount already activated.
(when (featurep 'cygwin-mount)
  (let ( (path (expand-file-name "~")) )
    (when (string-match "\\([c-z]\\):/" path)
      (setenv "MANPATH" (concat "/cygdrive/" (substring path 0 1) "/" (substring path 3) "/usr/share/man/:"))
      ) ))

;; I prefer EN man pages.
(when (memq system-type '(windows-nt cygwin))
  (setq manual-program "LANG=C man")
  )

(setq recentf-save-file "~/.recentf")
(when (eq system-type 'cygwin)
  (setq recentf-save-file "~/.recentf-cygwin"))

(setq desktop-base-file-name ".emacs.desktop")
(setq desktop-base-lock-name ".emacs.desktop.lock")
(when (eq system-type 'cygwin)
  (setq desktop-base-file-name ".emacs.desktop-cygwin")
  (setq desktop-base-lock-name ".emacs.desktop-cygwin.lock")
  )




-- 
Best regards!

Re: How to build the C language environment in Emacs?

[Óscar Fuentes]

Quanyang Liu <lqymgt@gmail.com> writes:

> well...IIRC, using Emacs in windows is terrible...

Not as easy as in GNU/Linux, but fairly good nonetheless. The "problem"
Emacs has on Windows is external dependencies. Tools such as `grep' are
always intalled on a GNU/Linux box, but you do have to install them
yourself on Windows. Those tools are not hard requirements for a working
Emacs, though.

Others mentioned Cygwin and IMHO it is the wrong solution. MSYS2 is
better because it doesn't pretend that Windows is a POSIX system.

Re: How to build the C language environment in Emacs?

[Ken Goldman]

On 1/3/2015 4:04 AM, Quanyang Liu wrote:
>
> well...IIRC, using Emacs in windows is terrible...

I use emacs on Windows and it's nearly the same as Unix.  Some of the 
PrintScreen ScrollLock Pause key chords don't work quite the same. 
Otherwise, emacs is emacs.

Re: How to build the C language environment in Emacs?

[Emanuel Berg]

Ken Goldman <kgoldman@us.ibm.com> writes:

>> well...IIRC, using Emacs in windows is terrible...
>
> I use emacs on Windows and it's nearly the same as
> Unix. Some of the PrintScreen ScrollLock Pause key
> chords don't work quite the same. Otherwise, emacs
> is emacs.

I also recall using Emacs in Windows unpleasant to say
the least.

Emacs is Emacs to some extent but Emacs doesn't exist
in a vacuum. If you use it on Windows you will miss
out a lot: convenience (everyone assumes you're on
some Unix); you miss out culture and technology.

And especially if you are into C - which is the number
one *system* programming language. It shares history
with UNIX, not to mention it is the language the
system is written in (including today's Linux).

There is no reason to use Windows for no reason, only
do it if your family is starving or your job is
super-exciting (like some science project where some
specific software is Windows-only and too intense for
wine and the like - but then you can still beam the
results to your Linux box and use Emacs to compile the
report - like I always said, computing is creative :))

-- 
underground experts united

Re: How to build the C language environment in Emacs?

[Quanyang Liu]

On Wed, Jan 07 2015 at 09:41:35 +0800, Emanuel Berg wrote:
> Ken Goldman <kgoldman@us.ibm.com> writes:
>
>>> well...IIRC, using Emacs in windows is terrible...
>>
>> I use emacs on Windows and it's nearly the same as
>> Unix. Some of the PrintScreen ScrollLock Pause key
>> chords don't work quite the same. Otherwise, emacs
>> is emacs.
>
> I also recall using Emacs in Windows unpleasant to say
> the least.
>
> Emacs is Emacs to some extent but Emacs doesn't exist
> in a vacuum. If you use it on Windows you will miss
> out a lot: convenience (everyone assumes you're on
> some Unix); you miss out culture and technology.
>

Yeah, using Emacs in Windows is OK, except for missing many things...

But in my Windows, I still install Emacs since no other editors satisfy
me. :)

> And especially if you are into C - which is the number
> one *system* programming language. It shares history
> with UNIX, not to mention it is the language the
> system is written in (including today's Linux).
>
> There is no reason to use Windows for no reason, only
> do it if your family is starving or your job is
> super-exciting (like some science project where some
> specific software is Windows-only and too intense for
> wine and the like - but then you can still beam the
> results to your Linux box and use Emacs to compile the
> report - like I always said, computing is creative :))

Well, in fact, in order to visit some websites, I need Windows because
they are IE only...

Ahh, I know virtual machines. I have been using it, so I do not open my
Windows for several months :)

After all, having a Windows is necessary...But I hope someday I can
uninstall it.

Re: How to build the C language environment in Emacs?

[Óscar Fuentes]

Quanyang Liu <lqymgt@gmail.com> writes:

> On Wed, Jan 07 2015 at 09:41:35 +0800, Emanuel Berg wrote:
>>>> well...IIRC, using Emacs in windows is terrible...
>>
>> I also recall using Emacs in Windows unpleasant to say
>> the least.
>>
>> Emacs is Emacs to some extent but Emacs doesn't exist
>> in a vacuum. If you use it on Windows you will miss
>> out a lot: convenience (everyone assumes you're on
>> some Unix); you miss out culture and technology.
>>
>
> Yeah, using Emacs in Windows is OK, except for missing many things...

Can you both provide hard facts instead of vague FUD about what makes
Emacs on Windows an unpleasant experience?

My Emacs setup is far from trivial and I couldn't say on which OS I am
using by just observing how I interact with Emacs. Gnus, Org, Evil,
Magit, AUCTeX, a dozen minor packages, 2000+ lines on .emacs and coding
on multipe programming languages, all is the same, except for the few
customizations that tells Emacs the directories where certain
executables and data files are stored.

Re: How to build the C language environment in Emacs?

[Emanuel Berg]

Óscar Fuentes <ofv@wanadoo.es> writes:

> Can you both provide hard facts instead of vague FUD
> about what makes Emacs on Windows an unpleasant
> experience?

I have been in exactly this discussion before. Even
then there were people who said it isn't the same at
all (and provided examples), and there were also
people who got agitated and said "its exactly the
same, what are you talking about, oh oh oh".

I can mention dozens of things that are different
running Emacs in a Linux VT compared to running it on
Windows. Probably hundreds but I stopped doing it on
Windows after two or three days and I won't do it
again.

But what is different: the colors and how to set them
up, retrieval and installation of Emacs itself, how to
invoke it, how you get additional software (e.g.,
LaTeX components, and Emacs-w3m), what such software
is available, how Emacs interacts with the rest of the
system - it doesn't have to be IPC with named pipes or
anything that fancy (but that would be different as
well, because of the different OS models) - it can be
as simple as the clipboard interaction with tmux and
X, all that just recently discussed would be totally
unapplicable; the keys, and how to setup special keys;
not to mention Windows in itself as a laughably
bloated and annoying system with popups and nuclear
wars all the time running amok in the, eh,
"background".

Windows is a joke. No excuses!

-- 
underground experts united

Re: How to build the C language environment in Emacs?

[Óscar Fuentes]

Emanuel Berg <embe8573@student.uu.se> writes:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> Can you both provide hard facts instead of vague FUD
>> about what makes Emacs on Windows an unpleasant
>> experience?
>
> I have been in exactly this discussion before. Even
> then there were people who said it isn't the same at
> all (and provided examples), and there were also
> people who got agitated and said "its exactly the
> same, what are you talking about, oh oh oh".
>
> I can mention dozens of things that are different
> running Emacs in a Linux VT compared to running it on
> Windows. Probably hundreds but I stopped doing it on
> Windows after two or three days and I won't do it
> again.
>
> But what is different: the colors and how to set them
> up, retrieval and installation of Emacs itself, how to
> invoke it, how you get additional software (e.g.,
> LaTeX components, and Emacs-w3m), what such software
> is available, how Emacs interacts with the rest of the
> system - it doesn't have to be IPC with named pipes or
> anything that fancy (but that would be different as
> well, because of the different OS models) - it can be
> as simple as the clipboard interaction with tmux and
> X, all that just recently discussed would be totally
> unapplicable; the keys, and how to setup special keys;

The only remote relation with Emacs usability is the lack of a package
management system on Windows (well, we have MSYS2 now, but still no
match for a Linux distro.) The rest of your diatribe consists on
"Windows is not Linux and I like Linux very much, therefore Windows is
garbage." (colors? keys? IPC? what are you talking about?)

> not to mention Windows in itself as a laughably
> bloated and annoying system with popups and nuclear
> wars all the time running amok in the, eh,
> "background".
>
> Windows is a joke. No excuses!

I'll be charitable and assume that your entire message is a joke.

Please stop spreading misinformation about the usability of Emacs on
Windows. You are damaging the Emacs project and insulting those who
contributed countless hours of their time to Emacs Windows support.

Re: How to build the C language environment in Emacs?

[Will Parsons]

Óscar Fuentes wrote:
> Emanuel Berg <embe8573@student.uu.se> writes:
>
> The only remote relation with Emacs usability is the lack of a package
> management system on Windows (well, we have MSYS2 now, but still no
> match for a Linux distro.) The rest of your diatribe consists on
> "Windows is not Linux and I like Linux very much, therefore Windows is
> garbage." (colors? keys? IPC? what are you talking about?)
>
>> not to mention Windows in itself as a laughably
>> bloated and annoying system with popups and nuclear
>> wars all the time running amok in the, eh,
>> "background".
>>
>> Windows is a joke. No excuses!
>
> I'll be charitable and assume that your entire message is a joke.
>
> Please stop spreading misinformation about the usability of Emacs on
> Windows. You are damaging the Emacs project and insulting those who
> contributed countless hours of their time to Emacs Windows support.

Indeed.  I've been using Emacs under Windows for around 15 years now,
and wouldn't dream of using anything else.  Thank you Emacs developers
for providing a powerful editor that that can be used so effectively
under *both* Unix-type OS's *and* Windows.

-- 
Will

Re: How to build the C language environment in Emacs?

[Rusi]

On Wednesday, January 7, 2015 7:51:57 PM UTC+5:30, Óscar Fuentes wrote:
> The only remote relation with Emacs usability is the lack of a package
> management system on Windows

You make that sound minor. I would say its a big plus for linux.

[And no I am not an anti-windows nut - there are things in windows
that are distinctly more advanced than in linux 
eg. the orderly registry vs the rag-tag bunch of files in /etc
]

Re: How to build the C language environment in Emacs?

[Óscar Fuentes]

Rusi <rustompmody@gmail.com> writes:

> On Wednesday, January 7, 2015 7:51:57 PM UTC+5:30, Óscar Fuentes wrote:
>> The only remote relation with Emacs usability is the lack of a package
>> management system on Windows
>
> You make that sound minor. I would say its a big plus for linux.

But we are not comparing Windows vs. Linux. I'm disputing the claim that
"using Emacs on Windows is terrible". If the issue is the lack of a
package system, Emacs is not different from any other Windows
application.

Re: How to build the C language environment in Emacs?

[Eli Zaretskii]

> Date: Wed, 7 Jan 2015 09:48:38 -0800 (PST)
> From: Rusi <rustompmody@gmail.com>
> Injection-Date: Wed, 07 Jan 2015 17:48:39 +0000
> 
> On Wednesday, January 7, 2015 7:51:57 PM UTC+5:30, Óscar Fuentes wrote:
> > The only remote relation with Emacs usability is the lack of a package
> > management system on Windows
> 
> You make that sound minor. I would say its a big plus for linux.

It's minor because it's not needed on Windows.

Re: How to build the C language environment in Emacs?

[Emanuel Berg]

Quanyang Liu <lqymgt@gmail.com> writes:

> Yeah, using Emacs in Windows is OK, except for
> missing many things...

Those were the things I meant :)

> But in my Windows, I still install Emacs since no
> other editors satisfy me. :)

I can't say I know the Windows editor world. Is Vim on
Windows? ("Wim"?)

The MS GUI IDEs (e.g., Access, VB5) do come with their
own editors, of course - very annoying because an
editor should let you do *all* editing, otherwise you
won't learn "everything" by doing "something" (or at
the very least it will come much, much slower).

> Well, in fact, in order to visit some websites, I
> need Windows because they are IE only...

Ha ha, stop it. There are no such sites. If there are,
I don't want to know their contents...

> Ahh, I know virtual machines. I have been using it,
> so I do not open my Windows for several months :)

Using VMs with Windows I actually do think counts as
using Windows :)

> After all, having a Windows is necessary...But I
> hope someday I can uninstall it.

How about today?

Remember: "What you once feared know makes you free -
do it today, in a different way."

Windows is absolutely not necessary. Food and shelter
and are necessary. Go to San Fernandez and find out.
God helps those who help themselves. He is especially
grateful to folks who do different, difficult things,
and if they do them long enough he rewards them with
skills and self-confidence: and much better tools, of
course.

-- 
underground experts united

Re: How to build the C language environment in Emacs?

[Bob Proulx]

Emanuel Berg wrote:
> Quanyang Liu writes:
> > Well, in fact, in order to visit some websites, I
> > need Windows because they are IE only...
> 
> Ha ha, stop it. There are no such sites. If there are,
> I don't want to know their contents...

I have experienced those first hand too.  Usually because the large
corporate employer I worked for used them for my payroll.  Meaning
that I could only ignore the IE only site if I didn't want my
paycheck.  If I wanted my paycheck then it was required to use IE to
talk to the IE only company payroll website.

Now that I have pulled the ejection handles and left the large
corporate employer I can blissfully ignore those abominations.  But I
still feel sympathy for those trapped in the system and the choice is
either stand on principle or feed the family.  Given that choice most
people suck it up, swallow their principles, and run IE to put food on
the table.

Bob

Re: How to build the C language environment in Emacs?

[Marcin Borkowski]

On 2015-01-07, at 20:37, Bob Proulx <bob@proulx.com> wrote:

> Emanuel Berg wrote:
>> Quanyang Liu writes:
>> > Well, in fact, in order to visit some websites, I
>> > need Windows because they are IE only...
>> 
>> Ha ha, stop it. There are no such sites. If there are,
>> I don't want to know their contents...
>
> I have experienced those first hand too.  Usually because the large
> corporate employer I worked for used them for my payroll.  Meaning
> that I could only ignore the IE only site if I didn't want my
> paycheck.  If I wanted my paycheck then it was required to use IE to
> talk to the IE only company payroll website.

Unfortunately, I have to confirm the sightings of these...  Not exactly
my payroll, but some e-learning materials (not done by me) which had
good content, but ran only on IE.

> Bob

Best,

-- 
Marcin Borkowski               This email was proudly sent
http://mbork.pl                from my Emacs.

Re: How to build the C language environment in Emacs?

[Eric Abrahamsen]

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> On 2015-01-07, at 20:37, Bob Proulx <bob@proulx.com> wrote:
>
>> Emanuel Berg wrote:
>>> Quanyang Liu writes:
>>> > Well, in fact, in order to visit some websites, I
>>> > need Windows because they are IE only...
>>> 
>>> Ha ha, stop it. There are no such sites. If there are,
>>> I don't want to know their contents...
>>
>> I have experienced those first hand too.  Usually because the large
>> corporate employer I worked for used them for my payroll.  Meaning
>> that I could only ignore the IE only site if I didn't want my
>> paycheck.  If I wanted my paycheck then it was required to use IE to
>> talk to the IE only company payroll website.
>
> Unfortunately, I have to confirm the sightings of these...  Not exactly
> my payroll, but some e-learning materials (not done by me) which had
> good content, but ran only on IE.
>
>> Bob

Online banking websites in large swathes of Asia. Try getting around
that!

Actually I take that back, the advent of Android apps has obviated the
problem to a large extent.

Re: How to build the C language environment in Emacs?

[Robert Thorpe]

Bob Proulx <bob@proulx.com> writes:

> Emanuel Berg wrote:
>> Quanyang Liu writes:
>> > Well, in fact, in order to visit some websites, I
>> > need Windows because they are IE only...
>> 
>> Ha ha, stop it. There are no such sites. If there are,
>> I don't want to know their contents...
>
> I have experienced those first hand too.  Usually because the large
> corporate employer I worked for used them for my payroll.  Meaning
> that I could only ignore the IE only site if I didn't want my
> paycheck.  If I wanted my paycheck then it was required to use IE to
> talk to the IE only company payroll website.

I worked for a company that had a complicated and finicky web-based
system for submitting expenses claims.  Some of it only worked in IE and
other bits of it only worked properly in Firefox.  It was necessary to
close the session in one browser and re-open it in another to file a
claim of any complexity.

BR,
Robert Thorpe

Re: How to build the C language environment in Emacs?

[Ken Goldman]

On 1/6/2015 8:41 PM, Emanuel Berg wrote:

> I also recall using Emacs in Windows unpleasant to say
> the least.
>
> Emacs is Emacs to some extent but Emacs doesn't exist
> in a vacuum. If you use it on Windows you will miss
> out a lot: convenience (everyone assumes you're on
> some Unix); you miss out culture and technology.

I use emacs on Windows and Linux, and even share 99% of my .emacs.  I 
frankly don't see what's missing.

Re: How to build the C language environment in Emacs?

[Eli Zaretskii]

> Date: Sat, 3 Jan 2015 13:34:59 +0900 (KST)
> From: Liu Shengyu<suzylau@kaist.ac.kr>
> 
> 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.

Can you compile from the cmd window?  If you cannot, then your MinGW
installation is broken, and this is not an Emacs problem.  You need to
fix that first.

If you can compile from the cmd window, but not from Emacs, then your
PATH and the list of directories where Emacs looks for programs are
different.  To make them identical, do NOT change PATH from the cmd
window, but instead from the Computer Properties, in the Advanced
section.

Re: How to build the C language environment in Emacs?

[Pascal J. Bourguignon]

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. 

What do you do to compile C files?

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html



> 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.

That would be ~/.emacs

> So can you help me about this question?

Hardly.  Read the above url.



> 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?

This is not emacs lisp syntax, but Common Lisp syntax.  Therefore you
will have to install a Common Lisp implementation.
Check: http://cliki.net/Getting+Started

-- 
__Pascal Bourguignon__                 http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk

Re: How to build the C language environment in Emacs?

[Emanuel Berg]

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

Re: How to build the C language environment in Emacs?

[Pascal J. Bourguignon]

Robert Thorpe <rt@robertthorpeconsulting.com> writes:

> Bob Proulx <bob@proulx.com> writes:
>
>> Emanuel Berg wrote:
>>> Quanyang Liu writes:
>>> > Well, in fact, in order to visit some websites, I
>>> > need Windows because they are IE only...
>>> 
>>> Ha ha, stop it. There are no such sites. If there are,
>>> I don't want to know their contents...
>>
>> I have experienced those first hand too.  Usually because the large
>> corporate employer I worked for used them for my payroll.  Meaning
>> that I could only ignore the IE only site if I didn't want my
>> paycheck.  If I wanted my paycheck then it was required to use IE to
>> talk to the IE only company payroll website.
>
> I worked for a company that had a complicated and finicky web-based
> system for submitting expenses claims.  Some of it only worked in IE and
> other bits of it only worked properly in Firefox.  It was necessary to
> close the session in one browser and re-open it in another to file a
> claim of any complexity.

And those programmers could still watch themselves in the mirrors each
morning?


-- 
__Pascal Bourguignon__                 http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk

Re: How to build the C language environment in Emacs?

[Nicolas Richard]

"Pascal J. Bourguignon" <pjb@informatimago.com> writes:
> Robert Thorpe <rt@robertthorpeconsulting.com> writes:
>> Bob Proulx <bob@proulx.com> writes:
>> I worked for a company that had a complicated and finicky web-based
>> system for submitting expenses claims.  Some of it only worked in IE and
>> other bits of it only worked properly in Firefox.  It was necessary to
>> close the session in one browser and re-open it in another to file a
>> claim of any complexity.
>
> And those programmers could still watch themselves in the mirrors each
> morning?

Well, they had to use two mirrors, making sure to turn off the light
in between, in order to get the whole picture.

-- 
Nico