[Conkeror] conkeror roadmap

[John J Foerch]

Luca Capello <luca at pca.it> writes:
> Hi John!
>
> I know how conkeror works (at least the how it worked one month ago,
> also the stand-alone version) and I know that it has buffers.  This is
> exactly what I don't like and why I specified "I don't like having
> multiple *frames*".
>
> Let me elaborate: my workflow is to have only one browser X window,
> fully of different tabs.  The same is possible on emacs-w3m, which
> doesn't have its own X window (I use exclusively `emacs -nw`), but it
> has its own Emacs frames, as my Gnus, Erc and the other Emacs stuff
> have.  So, I can switch to Gnus by selecting the appropriate frame,
> the same for Erc, emacs-w3m and so on.
>
> FWIW, as you surely already know, every Emacs frame has an X window
> when you use a "graphical" Emacs is started with X support.  That's
> why in my first reply I use the word "multiple frames".
>
> Conkeror, however, shows only one buffer (or tab, which is not the
> same, but the end result yes) at the time, creating an X window for
> every buffer you open.  Instead, I'd like to have all the buffers in
> one X window, thus tabbed browsing.
>
> ATM, this the main stopper for me to fully adopt Conkeror.
>

Hi Luca,

Are you referring to conkeror's behavior when you send an url to it
from another application?  (this is call "command line remoting")
If that is what you mean, you can put the following line in your rc file:

  conkeror.url_remoting_fn = conkeror.find_url_new_buffer;

Then running `conkeror http://www.foo.com' would open foo.com in a new
buffer instead of a new frame.

--John