[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] Crash report - segfault reproduceable

From: Nick Warne
Subject: Re: [Nano-devel] Crash report - segfault reproduceable
Date: Mon, 30 Jan 2006 21:01:36 +0000
User-agent: KMail/1.9

On Monday 30 January 2006 20:44, Nick Warne wrote:
> On Monday 30 January 2006 20:40, Mike Frysinger wrote:
> > you seem to have forgotten that other people have experienced this issue
> > as well :)
> *phew*
> > when you use putty, what is your TERM set to ?
> Whatever default is - but I did try experimenting and changed it a bit -
> all to no avail.
> Remember, nano works perfect 99.99% of the time (it is only editor I use on
> all 10 odd machines I use).  Once before I had this segfault, but could
> never reproduce.  It was only after editing a file sent to me that it
> happened again, so I looked at it in vi - and saw a really long line with
> lots of tabs at the end... that is how I found what caused the segfault for
> me, and made it reproduceable.

Could it be an environment setting?  Sort of my default bashrc file stuff:


shopt -s histappend
PROMPT_COMMAND='history -a'

export HISTCONTROL=ignoredups

export EDITOR=nano
# for crontab
export VISUAL=nano

"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb

reply via email to

[Prev in Thread] Current Thread [Next in Thread]