From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Mysterious hidden end of line characters.
Date: Thu, 31 Jan 2008 17:21:38 +1100 [thread overview]
Message-ID: <871w7yms5p.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.6748.1201705322.18990.help-gnu-emacs@gnu.org
David <dpleydel@univ-fcomte.fr> writes:
>
> Ha ha, I thought someone might spot this. After 2 years of emacs use I
> still have one or two newbie feathers lerking in my plummage. I do use
> *shell* buffers alot, but there is some terminal functionality which I
> do not have.
>
> Examples of commands in a *shell* buffer which for me don't work as in
> a terminal include
>
> 1) shell_prompt:~$ man pwd ## (or any other command), this gives
> something rather unfriendly in emacs. Only today did I discover M-x
> man was the proper way to do this. Nice feature, but rather
> non-evident to the newbie. Why is *shell* not totally equivelent to a
> terminal?
The command M-x shell gives you a 'dumb' terminal. This means any
program that relies on terminal IO to display correctly wil fail. for
programs like this, use M-x term.
>
> 2) shell_prompt:~$ grass ## Similarly to typing man at the prompt, the
> lack of terminal functionality used to prevent me from passing the
> terminal based setup page. I recently discoverred the solution (for
> older versions of GRASS) was to add a flag specifying a GUI setup
> page. Also updating to more recent versions appears to avoid this
> problem. So now I am finally using GRASS in emacs (horrah!).
>
Again, M-x term may be a better solution. Of course, you could just
write a special grass-mode and stick it up on emacswiki :)
> 3) shell_prompt:~$ mutt ## Similarly, I cannot find a way to navigate
> my mail boxes using mutt inside emacs. Emacs just isn't displaying
> anything that would normally appear in the terminal apart from when I
> hit q it asks if I really want to quit - of course I do, I can't see
> anything! The best I can do is to run mutt in the terminal, pass to
> emacs to write messages and pass back to the terminal to handle
> attachments etc. What am I missing?
>
I think there may be amode out there for running mutt in emacs. However,
maybe switch to a native emacs mail client. If you use IMAP, you could
use one of the many emacs mail clients that support imap and then when
your not in emcs, you can use mutt and still have access to all your
mail. There are also interfaces to gmail.
> 4) shell_prompt:~$ su ## I never like moving to super user in emacs
> because the password appears on screen as I type it. So all
> administration is terminal based for me. How to hide passwords as a
> terminal would?
>
I don't get this problem using M-x term
I also use tramp to edit files owned by others from within emacs
i.e. /root@localhost:/path/to/file
Use M-x shell only when you want to execute simple line oriented
programs that don't need things like ncurses or formatted screen IO.
finally, if your someone who likes to use lisp at the shell level and
have nice integration with emacs, have a look at the emacs shell - type
M-x eshell
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-01-31 6:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:14 Mysterious hidden end of line characters David
2008-01-26 19:21 ` Thierry Volpiatto
2008-01-26 19:54 ` David
2008-01-26 20:06 ` David
2008-01-26 20:08 ` David
[not found] ` <mailman.6584.1201377847.18990.help-gnu-emacs@gnu.org>
2008-01-27 6:10 ` Tim X
2008-01-27 7:17 ` kgdb in emacs Sanjeev Kumar.S
2008-01-27 8:26 ` Nick Roberts
2008-01-27 8:53 ` Sanjeev Kumar.S
2008-01-27 9:23 ` Nick Roberts
2008-01-27 10:17 ` Sanjeev Kumar.S
2008-01-27 10:51 ` Nick Roberts
2008-01-27 11:21 ` Sanjeev Kumar.S
2008-01-27 20:40 ` Nick Roberts
2008-01-26 20:41 ` Mysterious hidden end of line characters Peter Dyballa
2008-01-30 15:04 ` David
[not found] ` <mailman.6748.1201705322.18990.help-gnu-emacs@gnu.org>
2008-01-31 6:21 ` Tim X [this message]
2008-01-31 10:20 ` Thierry Volpiatto
2008-01-31 11:17 ` Peter Dyballa
2008-01-31 12:44 ` Thierry Volpiatto
2008-01-31 16:04 ` Thierry Volpiatto
2008-01-31 16:12 ` Thierry Volpiatto
2008-01-31 16:40 ` Thierry Volpiatto
2008-02-02 14:18 ` Thierry Volpiatto
2008-02-04 13:00 ` Thierry Volpiatto
2008-02-04 13:10 ` Thierry Volpiatto
[not found] <20080131144200.566493BC03B@ufc.univ-fcomte.fr>
2008-01-31 16:36 ` David
[not found] <20080131170759.CC0B71BC00C@ufc.univ-fcomte.fr>
2008-01-31 17:54 ` David
2008-01-31 18:28 ` Thierry Volpiatto
2008-02-01 12:54 ` David
2008-02-01 14:07 ` Thierry Volpiatto
2008-02-01 15:11 ` Thierry Volpiatto
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=871w7yms5p.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--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).