On Wed, 2011-05-11 at 23:11 +1000, Reiner Pope wrote:
>
> * Can you think of an example where you would want to have
> multiple
> miniwindows open concurrently? Emacs and (apparently) vi don't
> support this.
I think if in emacs mode you have 2 windows opened and enter the C-x C-
Ok, this is quite reasonable. At the same time, I don't understand how do
you see installation process.
Suppose user doesn't have any config.
cabal install yi
cabal install yi-pango
How will Yi select UI for him, since it's not hardcoded in configuration
file yet?
2011/5/11 Jean-Philippe Bernard
On 11/05/11 23:45, Jean-Philippe Bernardy wrote:
On Wed, May 11, 2011 at 3:11 PM, Reiner Pope wrote:
On 11/05/11 17:27, Jean-Philippe Bernardy wrote:
Rather than adding a new window type, It would be a lot easier to
1. Change the layout algorithm to put mini windows at the bottom
2. Creatio
On Wed, May 11, 2011 at 4:00 PM, Max Cantor wrote:
> Alternatively, you could have Yi just be a library which front-end's link to.
> then, only the front-ends have binaries. no linking issues, no plugins, far
> simpler dependency checks, easier for people unrelated to the project to
> write n
Alternatively, you could have Yi just be a library which front-end's link to.
then, only the front-ends have binaries. no linking issues, no plugins, far
simpler dependency checks, easier for people unrelated to the project to write
new front ends..
cabal install yi-cocoa
cabal install yi-vty
On Wed, May 11, 2011 at 3:30 PM, wrote:
> Do you mean keeping UIs in the same package with core?
No; they can be separate.
> Or dropping the
> ability to select frontend on startup with cmd args?
No.
I am saying the configuration file can link to any number of UIs desired
(ff they are not ins
On Wed, May 11, 2011 at 3:11 PM, Reiner Pope wrote:
> On 11/05/11 17:27, Jean-Philippe Bernardy wrote:
>
> Rather than adding a new window type, It would be a lot easier to
>
> 1. Change the layout algorithm to put mini windows at the bottom
> 2. Creation of a miniwindow if one already exists.
>
>
Do you mean keeping UIs in the same package with core? Or dropping the
ability to select frontend on startup with cmd args?
Neither way seems fine for me.
--
Yi development mailing list
yi-devel@googlegroups.com
http://groups.google.com/group/yi-devel
On 11/05/11 17:27, Jean-Philippe Bernardy wrote:
Rather than adding a new window type, It would be a lot easier to
1. Change the layout algorithm to put mini windows at the bottom
2. Creation of a miniwindow if one already exists.
I'm not sure I understand your second point.
Regarding the fir
Why not just let the frontends link with the core statically?
After all re-configuration triggers a re-link.
Cheers,
JP.
On Wed, May 11, 2011 at 11:53 AM, wrote:
> Hello guys,
> Recently I've been thinking on splitting Yi into core package and UIs.
> Here are some of my thoughts:
> Currently Yi
Hello guys,
Recently I've been thinking on splitting Yi into core package and UIs.
Here are some of my thoughts:
Currently Yi core slightly depends on frontends.
This dependence can be easily removed(fix me if I'm wrong). However, it'll
no longer be possible to select frontend on startup with
On Wed, May 11, 2011 at 3:30 AM, Reiner Pope wrote:
> Thoughts?
Rather than adding a new window type, It would be a lot easier to
1. Change the layout algorithm to put mini windows at the bottom
2. Creation of a miniwindow if one already exists.
The logical position of the miniwindow in the st
Comment #1 on issue 349 by jeanphil...@gmail.com: Multiple minibuffers can
be opened; all but one treated as 'file' buffers
http://code.google.com/p/yi-editor/issues/detail?id=349
Here's a sane way to look at it: there are no "minibuffers", only
miniwindows.
Yi does not prevent opening a f
13 matches
Mail list logo
