[task #13097] In-buffer PRIVMSG proposal

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[task #13097] In-buffer PRIVMSG proposal

Eric L.-2
URL:
  <http://savannah.nongnu.org/task/?13097>

                 Summary: In-buffer PRIVMSG proposal
                 Project: WeeChat
            Submitted by: superuser
            Submitted on: Sat 15 Feb 2014 16:18:20 GMT
                Category: None
         Should Start On: Sat 15 Feb 2014 00:00:00 GMT
   Should be Finished on:
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
         Originator Name:
        Originator Email:
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
                IRC nick: Evropi

    _______________________________________________________

Details:

This proposal is in two parts:

=The easy part -- *outgoing messages*:=
Simply put, follow what other clients do. This could be a configurable option.
Ideally it would be the default as it's a de facto standard among clients to
present _/msg_ in this way.

When you use /msg to message someone, the PRIVMSG you sent appears in the
buffer you sent it from, not the server buffer.

This makes sense because the entry box is not buffer-independent, not to
mention that using _/msg_ from within a buffer makes more sense because you'd
expect people to tab-complete usernames in it.

---

=The hard part -- *incoming messages*:=
This proposal is modelled after how HexChat handles this. I suggest trying
this out to get a real feel for it. To do this, go to Settings -> Preferences
-> Channel switcher and uncheck "Open a New tab when you receive a private
message".

Here's _how it works_:

You're in two buffers on Freenode (_#weechat_, _#steamlug_ and _#defocus_) and
one on OFTC (_#osm_).

Your friend Bob, who sends you a PRIVMSG, is in _#defocus_ and _#steamlug_ on
Freenode.

* If you're looking at _#defocus_ or _#steamlug_, it just appears in-buffer.
* If you're looking at _#weechat_ or #osm (OFTC), it goes to the first in the
list which *both you and Bob* have joined, which in our case is _#steamlug_.
WeeChat buffer order can be arbitrary, and you've set up #defocus to come
last.

HexChat counts these as system messages (like quits/joins), which is not the
best implementation for notifying users.
Ideally WeeChat should handle them as it handles private messages already (so
beep.pl and stuff work out of the box).




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?13097>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[task #13097] In-buffer PRIVMSG proposal

Eric L.-2
Follow-up Comment #1, task #13097 (project weechat):

This idea is from Yaniel in #weechat:

It would be better for *incoming messages if:

* You are looking at a buffer both of you are in, show incoming messages
* You are looking at any other buffer, then create a new buffer (current
behaviour)

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?13097>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev