Benno Schulenberg wrote:
> Bob Proulx wrote:
> > I do not have a nanorc file at all. The defaults are okay for
> > suspension without any specific configuration.
>
> ?? How does that work? What version of nano are you using?
Since this has nothing to do bash I am going to take this to the nano
Benno Schulenberg wrote:
> Bob Proulx wrote:
> > [...] this is the perfect case for job control. No need for a
> > second terminal. Here is an example. Use Control-Z to stop the
> > foreground job.
>
> For that to work, it requires having 'set suspend' in your
> nanorc. (Which I don't have, be
On 16 Feb 2016 18:19, Bob Proulx wrote:
> Nick Warne wrote:
> > I was in a SSH session, and checking something inadvertently issued:
> >
> > > nano /var/log/messages | grep a
> >
> > (I was searching for something else than an 'a', but the above example shows
> > the issue - about to use 'nano',
OK, everybody,
Thanks for the replies. As I stated, it was me being stupid - why I
didn't think of Ctrl+Z I don't know - I have only been using GNU/Linux
for 14 years :)
Mind you, it was late and I was rushing to stop my Raspberry Pi
connecting to the AP rather than the range extender.
So
Nick Warne wrote:
> I was in a SSH session, and checking something inadvertently issued:
>
> > nano /var/log/messages | grep a
>
> (I was searching for something else than an 'a', but the above example shows
> the issue - about to use 'nano', but then forgot to change it to 'cat').
>
> The termi
Try a
Ctrl-X
That worked for me with the exact same command line as yours. It exits nano.
On Mon, Feb 15, 2016 at 11:24 AM, Nick Warne wrote:
> Hi Everybody,
>
> I ma not sure if this is a bug, or if it is what causes it - if it isn't,
> then it is me being stupid.
>
> I was in a SSH session,
