[Top][All Lists]

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

[Weechat-dev] [task #9228] Share the input line between buffers

From: FlashCode
Subject: [Weechat-dev] [task #9228] Share the input line between buffers
Date: Sat, 28 Mar 2009 23:50:45 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090314 Minefield/3.2a1pre


                 Summary: Share the input line between buffers
                 Project: Wee Enhanced Environment for Chat
            Submitted by: nnssj
            Submitted on: dim 29 mar 2009 00:50:44 CET
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
                IRC nick: 



It would be quite nice indeed if we were able to activate the sharing of the
current input line between buffers.

If this comes at the cost of losing local history, so be it, but it would be
awesome if both were possible.

Thanks for considering it.


Follow-up Comments:

Date: sam 19 nov 2005 17:33:32 CET  By: Peter Maydell <pm215>
I've committed a patch to the manpage to say that lower case envariables
aren't supposed to be set by the user, so this bug is fixed. (Change should
make it into 1.2.)

Date: lun 14 nov 2005 14:14:23 CET  By: Peter Maydell <pm215>
>The man page mh_profile(5) says, that one can set the default 
>editor used by whatnow by setting a $mheditor environment 

Actually, it doesn't (if you interpret it right). I think the idea is that
environment variables in uppercase are user-settable, and lowercase ones are
set only to communicate information from one part of nmh to another. The
explanatory text generally says 'this is set' rather than 'you can specify'.

It's clear from the code that whatnow does check the envariable; I assume the
original reporter found setting it had no effect because it was overridden by
whatever other bit of nmh was invoking whatnow.

My suggestion is that we should add something to the mh-profile manpage,
explaining this convention and that lowercase envariables aren't
user-settable. We could probably also put something more of a separator
between them and the user-settable envariables.


Reply to this item at:


  Message posté via/par Savannah

reply via email to

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