From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: Arash Farmand <arashfarmand@hotmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc
Date: Mon, 31 Mar 2003 08:09:00 -0000 [thread overview]
Message-ID: <3E87EE8F.4070104@longlandclan.hopto.org> (raw)
In-Reply-To: <vpqadfcuhnn.fsf@imag.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthieu Moy wrote:
> You'd better use "Hello world!\n", because the IO are usually buffered
> by your system, and will not appear until your process outputs a '\n'.
All the \n does is outputs a new line, so rather than the program doing
this:
[someuser@aunixmachine ~] $ ./a.out
Hello world![someuser@aunixmachine ~] $ _
it will put the newline on the end of the string, making it look like this:
[someuser@aunixmachine ~] $ ./a.out
Hello world!
[someuser@aunixmachine ~] $ _
Not sure about it not appearing at all. I think it would appear when
the program ends, but then again, I may be wrong.
>
> But the solution is to call ./a.out, or to add '.' to your $PATH
> environment variable :
>
> PATH=${PATH}:.
> export PATH
>
> using bash. (Type it once in every new shell, or put it in your
> ~/.bashrc file.)
>
Actually, if you've got root access, you can add the following line to
your /etc/profile, or as above, your ~/.bashrc file:
export PATH="$PATH:."
>
> BTW, forget about kwrite : you should use Emacs or vi ;-)
>
Actually, gVim may not be such a bad idea. It's vi, but has a
graphical frontend with menus, etc. Emacs, yeah, I've used it, not bad,
but I've become a vim person myself. Also, there's PICO (a really basic
editor), or Jed (quite a nice tool).
Nothing wrong with kwrite, it isn't too bad to use. Basically, use
anything you like, just make sure it spits the file out as plaintext
(nothing like MS Word formatting characters to add to the compiller
messages and mangle your code).
- --
+-------------------------------------------------------------+
| Stuart Longland stuartl at longlandclan.hopto.org |
| Brisbane Mesh Node: 719 http://stuartl.cjb.net/ |
| I haven't lost my mind - it's backed up on a tape somewhere |
| Griffith Student No: Course: Bachelor/IT @ Nathan |
+-------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1-nr1 (Windows 2000)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+h+6OIGJk7gLSDPcRAokfAJ4pUm501LEt1rls7xkjHsd7QWqxiQCdGho5
GUbrduHom4t3eemZ+LVGa8g=
=ALjO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-03-31 7:31 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 1:45 gcc Arash Farmand
2003-03-31 2:28 ` gcc Andre Kirchner
2003-03-31 7:31 ` gcc Matthieu Moy
2003-03-31 8:09 ` Stuart Longland [this message]
2003-03-31 13:28 ` gcc Matthieu Moy
2003-04-02 0:42 ` gcc Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 12:55 gcc Octavia Bennett
2022-11-03 14:56 gcc Jason Bloom
2021-11-26 9:24 gcc Claire Carter
2021-07-22 4:31 Gcc Alice Matthews
2021-07-14 19:25 Gcc Wendy Bonner
2020-11-07 18:08 gcc Simon Liu
2019-12-16 8:50 Gcc Isabella Kathryn
2012-06-07 9:36 gcc jai singh
2012-06-07 12:27 ` gcc Jonathan Wakely
2011-08-29 8:44 GCC emil johansson
2011-08-29 9:29 ` GCC David Brown
2011-08-29 16:32 ` GCC Philip Herron
2008-10-09 21:38 gcc Jair Santos
2008-10-10 10:24 ` gcc Andrew Haley
2006-06-03 10:24 gcc Gunnar Sjoo
2004-09-22 4:27 GCC Drew Gray
2004-09-22 12:48 ` GCC Ishwar Rattan
2004-03-25 23:13 gcc frostflare
2004-03-26 1:12 ` gcc Eljay Love-Jensen
2004-03-25 19:12 gcc frostflare
2004-03-25 19:13 ` gcc llewelly
2004-03-24 15:05 gcc faltat
2004-03-24 22:32 ` gcc Ken Foskey
2004-03-24 2:44 GCC faltat
2004-03-24 4:23 ` GCC Eljay Love-Jensen
2003-12-16 14:14 GCC Jerry Lyle
2003-09-04 20:55 gcc Rich Franczak
2003-09-04 23:42 ` gcc Eljay Love-Jensen
2003-03-31 7:19 gcc Dockeen
2003-03-30 7:24 gcc Arash Farmand
2003-03-30 15:50 ` gcc Bharathi S
2003-03-31 0:58 ` gcc LLeweLLyn Reese
[not found] <616BE6A276E3714788D2AC35C40CD18D86F76D@whale.softwire.co.uk>
2002-10-11 5:13 ` GCC Rupert Wood
2002-10-11 4:44 GCC Bruno Aulagner
2002-08-29 19:23 gcc Samuel Lee Kwek Ming
2002-08-29 19:27 ` gcc Ish Rattan
2002-08-30 3:42 ` gcc Claudio Bley
2002-08-19 19:23 gcc Samuel Lee Kwek Ming
2002-01-10 9:30 gcc Tom Fetterer
2001-02-15 7:50 gcc Robert Neal
2001-02-15 9:16 ` gcc Alexandre Oliva
2001-02-12 17:17 gcc Paramjit Cheema
2001-02-12 18:38 ` gcc Alexandre Oliva
2001-01-21 19:26 gcc Simon Ouellet
2001-01-21 19:48 ` gcc Alexandre Oliva
2000-05-29 8:16 gcc Blythe Dickman
2000-05-29 10:15 ` gcc Martin v. Loewis
2000-03-09 11:33 gcc Olaf Miller
2000-03-09 16:43 ` gcc Martin v. Loewis
2000-04-01 0:00 ` gcc Martin v. Loewis
2000-04-01 0:00 ` gcc Olaf Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E87EE8F.4070104@longlandclan.hopto.org \
--to=stuartl@longlandclan.hopto.org \
--cc=arashfarmand@hotmail.com \
--cc=gcc-help@gcc.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).