|
|
Up |
|
|
  |
Author: Francis MoreauFrancis Moreau Date: Sep 12, 2008 09:20
Hello,
I'm still trying to do all my jobs inside emacs but I'm missing a couple
things.
The first one is what I can't do anymore when working with a shell/terminal
inside emacs.
1/ Most applications based on ncurse behave strangely when using
M-x term
2/ Although M-x shell has history reference completions, it doesn't complete
for '!#:'. But '!!:' works fine though.
3/ There's no readline "reverse-search-history" function (C-r) which does
an _incremental_ search;
4/ There's no readline "yank-last-arg" function which inserts the last
argument to the previous commands
5/ emacs doesn't expand shell variable when hitting
Am I missing something ?
Thanks
--
Francis
|
| |
|
| | 25 Comments |
|
  |
Author: Dan EspenDan Espen Date: Sep 12, 2008 10:34
"Francis Moreau" gmail.com> writes:
> Hello,
>
> I'm still trying to do all my jobs inside emacs but I'm missing a couple
> things.
>
> The first one is what I can't do anymore when working with a shell/terminal
> inside emacs.
...
> Am I missing something ?
Maybe.
I do all my work inside emacs except for browsing
and 3270 emulation.
I've used M-x shell in the past but not for many years.
Compiles are M-x compile, greps are M-x grep,
ls is dired, email is MH-E.
Maybe most emacs users aren't that committed to M-x shell and
it's friends.
|
| |
|
| | no comments |
|
  |
Author: Oleksandr GavenkoOleksandr Gavenko Date: Sep 12, 2008 10:59
Francis Moreau wrote:
> 4/ There's no readline "yank-last-arg" function which inserts the last
> argument to the previous commands
Is the feature useful?
In C-x shell you can move cursor to select any previous typing and
pressing M-> to back to writing command.
|
| |
| no comments |
|
  |
Author: rustomrustom Date: Sep 12, 2008 23:10
On Sep 12, 9:20Â pm, "Francis Moreau" gmail.com> wrote:
> Hello,
>
> I'm still trying to do all my jobs inside emacs but I'm missing a couple
> things.
>
> The first one is what I can't do anymore when working with a shell/terminal
> inside emacs.
>
> Â 1/ Most applications based on ncurse behave strangely when using
> Â Â Â M-x term
>
> Â 2/ Although M-x shell has history reference completions, it doesn't complete
> Â Â Â for '!#:'. But '!!:' works fine though.
>
> Â 3/ There's no readline "reverse-search-history" function (C-r) which does
> Â Â Â an _incremental_ Â search;
>
> Â 4/ There's no readline "yank-last-arg" function which inserts the last
> Â Â Â argument to the previous commands ...
|
| Show full article (0.94Kb) |
| no comments |
|
  |
Author: Livin StephenLivin Stephen Date: Sep 13, 2008 01:08
On Sep 12, 9:20Â pm, "Francis Moreau" gmail.com> wrote:
> Hello,
>
> I'm still trying to do all my jobs inside emacs but I'm missing a couple
> things.
>
> The first one is what I can't do anymore when working with a shell/terminal
> inside emacs.
>
> Â 1/ Most applications based on ncurse behave strangely when using
> Â Â Â M-x term
>
> Â 2/ Although M-x shell has history reference completions, it doesn't complete
> Â Â Â for '!#:'. But '!!:' works fine though.
>
> Â 3/ There's no readline "reverse-search-history" function (C-r) which does
> Â Â Â an _incremental_ Â search;
>
> Â 4/ There's no readline "yank-last-arg" function which inserts the last
> Â Â Â argument to the previous commands ...
|
| Show full article (1.63Kb) |
| no comments |
|
  |
Author: Francis MoreauFrancis Moreau Date: Sep 13, 2008 01:27
[ please CC me when replying to me ]
On Fri, Sep 12, 2008 at 7:34 PM, Dan Espen
more.mk.spamtelcordia.com> wrote:
> Compiles are M-x compile, greps are M-x grep,
> ls is dired, email is MH-E.
But what would you suggest as replacement for:
$ make && gdb || mail -s "Compilation failed" home
More generally sh scripts allow automatisation processes that you
can't simply do with emacs commands, it similar to using a mouse
actually. I don't think you can get rid of them.
Futhermore there are a lot of tools out there that are not integrated
to emacs if you do so, you don't have enough keys on the keyboard to
create bindings ;)
So I don't think you can realistically get rid of a shell
> Maybe most emacs users aren't that committed to M-x shell and
> it's friends.
Probably.
|
| Show full article (1.01Kb) |
| no comments |
|
  |
Author: Francis MoreauFrancis Moreau Date: Sep 13, 2008 01:29
Hello,
On Fri, Sep 12, 2008 at 7:59 PM, Oleksandr Gavenko gmail.com> wrote:
> Francis Moreau wrote:
>>
>> 4/ There's no readline "yank-last-arg" function which inserts the last
>> argument to the previous commands
>
> Is the feature useful?
> In C-x shell you can move cursor to select any previous typing and pressing
> M-> to back to writing command.
>
Do you realize how many key pressings you're doing to do what you described ?
In my use case I only press one time.
--
Francis
|
| |
| 1 Comment |
|
  |
Author: Francis MoreauFrancis Moreau Date: Sep 13, 2008 01:36
Hello,
On Sat, Sep 13, 2008 at 8:10 AM, rustom gmail.com> wrote:
>
> shell's inadequacies in emacs are well known.
Do you have any pointers that describes them ?
> eshell often works better
I just try history reference completion, and it's even worse...
thanks
--
Francis
|
| |
| no comments |
|
  |
Author: Francis MoreauFrancis Moreau Date: Sep 13, 2008 02:00
Hello,
On Sat, Sep 13, 2008 at 10:08 AM, Livin Stephen gmail.com> wrote:
>
> YMMV, but I had to "export TERM=xterm" in my ~/.bashrc to make M-x
> term work as per expectations...
hmm I'm probably missing something here but why exporting TERM=xterm
would change anything since it is already if you're using a window
manager.
> - i.e. to be usable for everyday use: on my Mac I'm perfectly happy
> with it's behaviour now!
ah ok you're using a Mac, so that explains probably why you need to export TERM
> (previous value in M-x term term used to show $TERM to be eterm-color
> or something like that)
>
yes and that should be again the case. Let see:
$ TERM=xterm emacs
< M-x term>
$ echo $TERM
eterm-color
|
| Show full article (1.30Kb) |
| no comments |
|
  |
|
|
  |
Author: Livin Stephen SharmaLivin Stephen Sharma Date: Sep 13, 2008 04:21
2008/9/13 Francis Moreau gmail.com>
> Hello,
>
> On Sat, Sep 13, 2008 at 10:08 AM, Livin Stephen gmail.com>
> wrote:
>>
>> YMMV, but I had to "export TERM=xterm"...
>
> hmm I'm probably missing something here but why exporting TERM=xterm
> would change anything since it is already if you're using a window
> manager.
>
>> - i.e. to be usable for everyday use...
>
> ah ok you're using a Mac, so that explains probably why you need to export
> TERM
Actually, without exporting TERM, I saw emacs' term to show it to be
"eterm-color":
the need to export it was to get it to be "xterm" instead.
|
| Show full article (3.55Kb) |
| no comments |
|
|
|
|