Not sure I can go with that analysis.
To put it politely I don't think you've looked at the code and output in
enough detail.
Ignore the first 'trace' line - it just happens to be there.
The substantive issue - LINENO going backwards - occurs across four source
lines, two of which are blank, and in
On 9/1/21 2:10 PM, C. Yang wrote:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Description:
>
> Whenever I start my session, I'd like to automatically open emacs to a
> specific file.
>
> So, I added the emacs command to the bottom of my ~/.bashrc file. This
> opens emacs
>
> c
Hi Dale and Chet,
Thank you both for your responses and clarifications. Yes, I would like emacs
to behave as if I had typed it in the command line, in particular, to be able
to stop
and background it in the usual way.
I can confirm that adding `set -m` before the emacs command in .bashrc
On Thu, Sep 02, 2021 at 12:15:35PM -0400, C. Yang wrote:
> I can confirm that adding `set -m` before the emacs command in .bashrc results
>
> in the behavior I want with CTRL+Z. As I understand, `set -m` will enable job
>
> control features. This suffices for my use case.
>
>
>
> However, is
Hello.
Thank you. If you don't want to implement it yourself, I am at your
disposal. :) Just let me now.
Best regards
Přemysl
On 9/1/21 4:11 PM, Chet Ramey wrote:
On 8/31/21 3:25 PM, Lawrence Velázquez wrote:
On Tue, Aug 31, 2021, at 4:02 AM, Lawrence Velázquez wrote:
ksh does not blindly
On 9/2/21 12:15 PM, C. Yang wrote:
> However, is it possible that there may be further unexpected consequences,
> since bash is still waiting to complete initialization this entire time?
>
> For instance, if I stop and background emacs, then I find myself back to
> the bash
> shell. But technical
Could you please explain why? I thought the reason for the behavior
described in my original post was that bash does not complete initialization
until .bashrc completes, which doesn't happen until the emacs process started
from within it completes? And it sounds
On 9/2/21 5:06 PM, C. Yang wrote:
Could you please explain why? I thought the reason for the behavior
described in my original post was that bash does not complete
initialization until .bashrc completes, which doesn't happen until the
emacs process started from within it completes?
OK. You s
Ah, I understand it now. Thanks for explaining it to me so
patiently. This also means my issue is resolved. Thank you all again for your
help!Best, Cheshire On Thu, 02 Sep 2021 18:44:36 -0400 Chet
Ramey wrote On 9/2/21 5:06 PM, C. Yang wrote: > Could
yo
