That did it! I assumed it was some compile difficulty because the repo
version had emacs mode, and it changed when I switched. Didn't occur to me
that tmux might have started checking EDITOR/VISUAL or some other config
change between the two versions. Thanks for the help!
- M
On Wed, Jun 15,
Chas. Owens wrote:
> On Thu, Jun 16, 2011 at 06:32, Helmut Schneider
> wrote: snip
> > Although I don't like the idea to construct a script to make other
> > scripts work with tmux I must admit that it works fine.
> snip
>
> I am confused, isn't that what you are doing already with
> check_for_
On Thu, Jun 16, 2011 at 06:32, Helmut Schneider wrote:
snip
> Although I don't like the idea to construct a script to make other
> scripts work with tmux I must admit that it works fine.
snip
I am confused, isn't that what you are doing already with
check_for_root_and_start_screen.sh? All you ha
Do you have a `tty` command? that may show "/dev/tty1" vs "/dev/pts/3"
which could identify it.
There may be other environment settings you could consult as well...
You could output your environment to a file under each of Console and X and
then diff them.
On Wed, Jun 15, 2011 at 12:29 AM, Nich
have you tried just setting TERM to "screen" instead of "sccreen-256color"?
If I have my TERM set to a value my terminfo db doesn't have i don't see any
colors.
Granted, I also see lots of warnings from various programs...
At work i had to build something into my .bashrc to check if the -256color
Chas. Owens wrote:
> On Sat, Jun 11, 2011 at 17:16, Helmut Schneider
> wrote:
> > Chas. Owens wrote:
> >
> >> On Sun, May 29, 2011 at 04:23, Helmut Schneider
> >> wrote: snip
> >> > I have a script, more a wrapper, that checks for screen and sudo
> >> > and if neither screen or sudo are active