notion-general Mailing List for notion (Page 6)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

When will there be a new release of notion? I have seen a lot of work being
checked in but no downloads for a year.

Naaa, but it's (MOD + .) or (MOD+,)  isn't it?

On Fri, May 15, 2015 at 07:54:47AM -0500, Javier Rojas wrote:
> On vie, may 15, 2015 at 09:16:41AM -0300, Renato Cantão wrote:
> > Hello!
> > 
> > I'm new to Notion and I love it! Very fast and functional.
> > 
> > There is one small thing I miss from other tilers, though: a "back and
> > forth" workspace function.
> 
> I have the following in my cfg_notioncore.lua:
> 
>     defbindings("WScreen", {
>         ...
>         bdoc("Go to first region demanding attention or previously active one."),
>         kpress("Mod4+P", "mod_menu.grabmenu(_, _sub, 'focuslist')"),
> 
> That does basically what you ask.
> 
> > 
> > Let me explain: suppose I'm doing a task involving cycling between
> > workspaces 1 and 5. With workspace back and forth, with a single binding
> > (lets say Alt+Escape) I can switch from 1 to 5 as many times I'd like,
> > with no need to move my fingers from Alt+1 to Alt+5. Indeed, I don't
> > even need to remember which workspaces I'm switching back and forth.
> > 
> > Is this implemented in Notion? If not, is it easy?
> > 
> > Thanks a lot,
> > Renato.
> > 
> > 
> > ------------------------------------------------------------------------------
> > One dashboard for servers and applications across Physical-Virtual-Cloud 
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> > _______________________________________________
> > Notion-general mailing list
> > Not...@li...
> > https://lists.sourceforge.net/lists/listinfo/notion-general
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Notion-general mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-general

-- 
Wojtek Aniszewski
[Fr:  vôitek anichévsky]
[Eng: voyteck aanishevsky]
www: http://www.coria.fr/spip.php?auteur1606
 /^..^\      ,-------------------------------------,
( (••) ) ►►►►| My public GPG key ID: AC66485E      |
(|)_._(|)~   | please use email encryption!        |
             `-------------------------------------"

On vie, may 15, 2015 at 09:16:41AM -0300, Renato Cantão wrote:
> Hello!
> 
> I'm new to Notion and I love it! Very fast and functional.
> 
> There is one small thing I miss from other tilers, though: a "back and
> forth" workspace function.

I have the following in my cfg_notioncore.lua:

    defbindings("WScreen", {
        ...
        bdoc("Go to first region demanding attention or previously active one."),
        kpress("Mod4+P", "mod_menu.grabmenu(_, _sub, 'focuslist')"),

That does basically what you ask.

> 
> Let me explain: suppose I'm doing a task involving cycling between
> workspaces 1 and 5. With workspace back and forth, with a single binding
> (lets say Alt+Escape) I can switch from 1 to 5 as many times I'd like,
> with no need to move my fingers from Alt+1 to Alt+5. Indeed, I don't
> even need to remember which workspaces I'm switching back and forth.
> 
> Is this implemented in Notion? If not, is it easy?
> 
> Thanks a lot,
> Renato.
> 
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Notion-general mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-general

Hello!

I'm new to Notion and I love it! Very fast and functional.

There is one small thing I miss from other tilers, though: a "back and
forth" workspace function.

Let me explain: suppose I'm doing a task involving cycling between
workspaces 1 and 5. With workspace back and forth, with a single binding
(lets say Alt+Escape) I can switch from 1 to 5 as many times I'd like,
with no need to move my fingers from Alt+1 to Alt+5. Indeed, I don't
even need to remember which workspaces I'm switching back and forth.

Is this implemented in Notion? If not, is it easy?

Thanks a lot,
Renato.

Hello Notion community,

I have an odd problem and I guess it might not even be related to notion
itself, but I can not wrap my head around it. So here goes:

I have two machines, Gentoo (OpenRC) and Arch (systemd).
Gentoo: notion 3-2013030200
Arch: 20150118-1

The .xinitrc basically looks like this in both cases:
- eval $(ssh-agent); ssh-add; blalblab; exec notion

Now, when I do notioncore.restart() on Gentoo, all my windows (terminals
etc) stay open and the WM is restarted, like i'd expect it to. 

When I do a restart on Arch, all the child processes have quit.
Depending on how I call xinitrc (prefixed with ssh-agent) X even drops
back to the xdm login dialog.

Any pointers on where to start on this?

Please CC me, not on the list.
Johannes

-- 
Johannes Gilger <he...@ha...>
Web: http://heipei.net
Twitter: https://twitter.com/heipei
GitHub: https://github.com/heipei/

> Programmers with no clue about Emacs!? Where will the world end?
> 
Unfortunately, they're an army, some of whom I see everyday.
And I share your thoughts about key layout.
w

-- 
Wojtek Aniszewski
[Eng: voyteck aanishevsky]
[Fr:  vôytek anichévsky]

 /^..^\      ,-------------------------------------,
( (••) ) ----| My public GPG key ID: AC66485E      |
(|)_._(|)~   | please use email encryption!        |
             `-------------------------------------"

Hi,

I have been using Ion3, then Notion for "ages", and here follows my views 
on any tampering with the keybindings.

1. The road to hell is paved with good intentions.

2. The re-mapping of Meta-L from "nudge" to "lock window" was not only an 
   irritating surprise for an old fart like me, it was also an unecessary 
   nod towards MS Windows. Do we want Notion to be like Windows? No! Did
   GNU Emacs or vi change their key bindings when MS Word appeared? No!

3. Sort of a corollary of 2; What is the point of mimicking the key 
   bindings of another X11 window manager? How many of us change every 
   other day? I.m.h.o. this is definitely against one of the core ideas 
   in the original Ion manifesto; Long term usability counts, first day 
   impression not. 

   (Counter example: The Ubuntu distribution, perhaps others too, are
   kitted out with various Swedish, German, etc Dvorak keyboard layouts.
   The originators of those layouts have not considered that many users
   might be multilingual, that many Dvorak layout users may want to 
   switch -- often! -- between the various layouts. Well intended "opti-
   misations" have, unfortunately, increased the differences between the
   various national Dvorak layouts waaaay beyond the absolute minimum.)

4. Yes, the creator of Ion did not map the keys the way you wanted them 
   to be. You can remap them in your own computer to your heart's content.
   Once we start tampering with the official version, however, chances are 
   that 2 years down the road, someone else, inspired by yet another com-
   peting w.m., with a new bag of arguments and good intentions (see 1.), 
   will come along and tear up the key-bindings again.

So, please, hands off!

Apart from this, I am still in a state of shock after being hit by the 
fact that Ibus eats Ctrl-Space before Emacs has a chance to see it. This 
slip-up on the side of the Ibus developers could only happen if the 
programmer in charge, as well as all around him/her, were utterly 
oblivious of the importance of Emacs.

Programmers with no clue about Emacs!? Where will the world end?

Best Regards

Johannes

Hi,
My name's Martin, msx on irc and I'm a newcomer to Not-ion.
A few days ago when talking about spectrwm with another user on irc he talk
about Notion as "my other WM that I really like".
Being myself an spectrwm lover/fanboy because many of it's amenities and
KISS design I already find myself now embraced under the spell of Notion
^_^ as it took me watching a couple of videos on YT then installing the WM
to realize that I was using an absolutely underrated marvel.
Thanks every1 for crafting this beauty, I'm now following this list and
-devel.
Best regards,
-M.

On Thu, Jul 17, 2014 at 7:05 PM, Wojciech Aniszewski <ani...@co...>
wrote:

> > I would warmly appreciate any help with:
> > * Creating a more modern theme
> what does 'modern' mean? example?
> sites like awesomes' are extremely zen:)
>

Oh yeah, that (http://awesome.naquadah.org/) looks pretty great! Doesn't
have to be fancy :).

Kind regards,

Arnout

Hi
> I would warmly appreciate any help with:
> * Creating a more modern theme
what does 'modern' mean? example?
sites like awesomes' are extremely zen:)
w

> * Creating a project frontpage (or migrating the existing one?)
> * Migrating the latex docs to github pages
> * Migrating the mediawiki content to github pages
> * Improving our documentation overall
> * Improving the presentation of our documentation overall (revisiting the
> tour it still seems like a very good introduction, but could be presented
> in a more friendly way)
> * Any ideas, feedback, tips, etc!
> 
> 
> Kind regards,
> 
> Arnout

> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft

> _______________________________________________
> Notion-general mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-general

-- 
Wojtek Aniszewski
[Eng: voyteck aanishevsky]
[Fr:  vôytek anichévsky]

 /^..^\      ,-------------------------------------,
( (••) ) ----| My public GPG key ID: AC66485E      |
(|)_._(|)~   | please use email encryption!        |
             `-------------------------------------"

On Sun, Jul 13, 2014 at 6:17 AM, Arnout Engelen <ar...@bz...> wrote:

>
>
>> Perhaps afterward we can chuck the LaTeX docs?
>
>
> Yes, that's the idea. LaTeX has served us well in the past, but it seems
> like it's time to move on. Using markdown and github-pages seems like a
> nice contributor-friendly workflow (though we'll still have to find a way
> to generate the API documentation and merge those).
>
>
Sounds good!

I haven't played with Github pages too much, so I'll need someone to point
>> me in the right direction. :)
>>
>
> I'm new to it, too. 'pandoc' seemed like a nice tool to convert latex
> files to markdown files. For the tables of contents, it seems 'kramdown',
> the markdown-to-html converter for github-pages, has some support for that.
> Beyond that, it's time to explore :).
>
>
> There is also LaTeXML <http://dlmf.nist.gov/LaTeXML/> which may be
useful. I'll get to digging. :)

Regards,
Jeff
-- 
Jeff Backus
jef...@gm...
http://github.com/jsbackus

On Sun, Jul 13, 2014 at 12:00 AM, Jeff Backus <jef...@gm...> wrote:

> On Thu, Jul 10, 2014 at 11:15:25PM +0200, Arnout Engelen wrote:
>
>> I would warmly appreciate any help with:
>>
> (..snip..)
>
>  * Migrating the latex docs to github pages
>>
>
> Hi Arnout,
>
> I can help poke at the LaTeX -> Github pages.

Cool!

> Perhaps afterward we can chuck the LaTeX docs?

Yes, that's the idea. LaTeX has served us well in the past, but it seems
like it's time to move on. Using markdown and github-pages seems like a
nice contributor-friendly workflow (though we'll still have to find a way
to generate the API documentation and merge those).

> I haven't played with Github pages too much, so I'll need someone to point
> me in the right direction. :)
>

I'm new to it, too. 'pandoc' seemed like a nice tool to convert latex files
to markdown files. For the tables of contents, it seems 'kramdown', the
markdown-to-html converter for github-pages, has some support for that.
Beyond that, it's time to explore :).

Kind regards,

Arnout

On Thu, Jul 10, 2014 at 11:15:25PM +0200, Arnout Engelen wrote:
>I would warmly appreciate any help with:
(..snip..)
>* Migrating the latex docs to github pages

Hi Arnout,

I can help poke at the LaTeX -> Github pages. Perhaps afterward we can 
chuck the LaTeX docs? I haven't played with Github pages too much, so 
I'll need someone to point me in the right direction. :)

Regards,
Jeff

Hi all,

The Notion site and documentation is currently kind of old-fashioned and
fragmented:

* Some static HTML pages on sf.net
* Some HTML/PDF documentation generated from latex sources
* A sf.net wiki that was discontinued (I have tar.gz and sql.gz backups,
but haven't looked into them yet)

We're long overdue for a switch to a more modern setup.

I'd like to move everything to jekyll/github-pages. As a crude first step I
moved over the 'tour' to http://raboof.github.io/notion/tour/ which is
generated from https://github.com/raboof/notion/blob/gh-pages/tour.md

I would warmly appreciate any help with:
* Creating a more modern theme
* Creating a project frontpage (or migrating the existing one?)
* Migrating the latex docs to github pages
* Migrating the mediawiki content to github pages
* Improving our documentation overall
* Improving the presentation of our documentation overall (revisiting the
tour it still seems like a very good introduction, but could be presented
in a more friendly way)
* Any ideas, feedback, tips, etc!

Kind regards,

Arnout

Jeff Backus <jef...@gm...> writes:

> On Sat, Jul 05, 2014 at 12:07:08AM -0700, Dima Kogan wrote:
>>Arnout Engelen <ar...@bz...> writes:
>>>
>>> Is anyone aware of any applications that solve this tension 
>>> gracefully?
>>> I.e. by prompting users on upgrade, perhaps telling them what changed and
>>> asking them whether they want to accept that change in their configuration?
>
> Unfortunately, this is a lot easier for most programs, as they have a 
> very finite "config domain", whereas Notion's config domain is not very 
> finite due to fact that options are variables set via Lua scripts. We 
> might be able to better automate handling changes to the config domain 
> if we used a "config manager" or similar construct. i.e. instead of:
>   focuslist_insert_delay = 5
> do:
>   conf_manager('focuslist_insert_delay', 5)
> which would allow us to better track how a user is configuring Notion 
> and to notify them of useful changes specific to their use-case.
>
> Another option might be to provide the user with a way to dump the Lua 
> namespace and compare it against the "new hotness". Not very graceful, 
> or user-friendly, though.

I'm not sure conf_manager helps you here. If a user isn't using the
defaults, but sets their own variable value, then us changing the
defaults has no effect. If the user IS using the defaults, then they
will not have "x=5" or "conf_manager('x',5)" lines, and they would see
the change.

There's much to say about all this, but it sounds very tricky to make
large changes like this without breaking the config of at least
somebody, so I'm inclined to mostly keep things the way they are and
simply announce breaking changes with clear instructions on how to move
back to the way things were.

>>Anybody got better ideas?
>
> Actually, a simple way we might be able to approximate Debian's NEWS 
> files on a distro-independent basis is to maintain a similar file gets 
> tucked away somewhere on the system. When Notion starts, it check 
> ~/.notion to for the file. If it doesn't exist or differs then Notion 
> could display the contents of the system-wide one then save a copy in 
> ~/.notion, similar to what happens with the welcome message for new 
> users.
>
> If we gzip or bzip2 the file, it should be pretty small and a binary 
> comparison should be pretty quick.  Plus, it wouldn't be dependent on 
> version numbers (i.e.  supports installing from git), as long as we were 
> diligent about updating it as we hack away at the codebase.
>
> The location of the system-wide file may need to be a compile option to 
> allow flexibility distro to distro and source installs. I dunno, just a 
> thought.

Sounds reasonable. It could work exactly like the welcome message: shown
just once.

Hi folks,

Sorry, been meaning to chime in since Arnout sent his initial e-mail.  
Been swamped. Therefore, I'll go ahead and respond to both in one. :)

On Sat, Jul 05, 2014 at 12:07:08AM -0700, Dima Kogan wrote:
>Arnout Engelen <ar...@bz...> writes:
>
>> I think a good out-of-the-box experience (i.e. good default settings)
>> is hugely important. On the other hand, a stable, hassle-free upgrade
>> path for existing users is equally essential.

Agreed on both accounts, though my preference is don't muck with the 
user's custom settings just because we think we know better. It can be 
quite aggravating to have behavior change without a warning. :)

Maybe ship with a conservative set of config files (like we do now) and 
a "new hotness" set, and encourage new users to use the "new hotness"? 

>> Is anyone aware of any applications that solve this tension 
>> gracefully?
>> I.e. by prompting users on upgrade, perhaps telling them what changed and
>> asking them whether they want to accept that change in their configuration?

Unfortunately, this is a lot easier for most programs, as they have a 
very finite "config domain", whereas Notion's config domain is not very 
finite due to fact that options are variables set via Lua scripts. We 
might be able to better automate handling changes to the config domain 
if we used a "config manager" or similar construct. i.e. instead of:
  focuslist_insert_delay = 5
do:
  conf_manager('focuslist_insert_delay', 5)
which would allow us to better track how a user is configuring Notion 
and to notify them of useful changes specific to their use-case. (With 
apologies to Dima's new feature - I have no idea how it works or how to 
configure it. O:-) )

Another option might be to provide the user with a way to dump the Lua 
namespace and compare it against the "new hotness". Not very graceful, 
or user-friendly, though.

>I don't know of any ways to handle this on a distro-independent basis.
>Since each distro handles installation and management of configuration
>files differently, there likely isn't anything that "just works" for
>everybody. This is a bit unsatisfying, but I think each distro
>maintainer has to handle the announcement of potentially-breaking
>changes themselves.
>
>Debian has NEWS.Debian files to do this:
>
> https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-news-debian
>
>We haven't yet released the new Debian packages with the changed
>defaults, but we'll use this when we do.
>
>For from-source installs, we should probably have a very loud
>announcement in the CHANGELOG. We currently do mention the change in
>that file, but it should probably be highlighted.
>
>Anybody got better ideas?

Actually, a simple way we might be able to approximate Debian's NEWS 
files on a distro-independent basis is to maintain a similar file gets 
tucked away somewhere on the system. When Notion starts, it check 
~/.notion to for the file. If it doesn't exist or differs then Notion 
could display the contents of the system-wide one then save a copy in 
~/.notion, similar to what happens with the welcome message for new 
users.

If we gzip or bzip2 the file, it should be pretty small and a binary 
comparison should be pretty quick.  Plus, it wouldn't be dependent on 
version numbers (i.e.  supports installing from git), as long as we were 
diligent about updating it as we hack away at the codebase.

The location of the system-wide file may need to be a compile option to 
allow flexibility distro to distro and source installs. I dunno, just a 
thought.

Oh, and Arnout, I do like the idea of adjusting the default key 
bindings, at least for new users and those wanting to switch. Function 
keys have unfortunately become part of the standard UI lexicon and it 
can be quite confusing to new users when they can't use them without 
additional key strokes. Particularly since one of Notion's selling 
points is "hey, that silly mouse thing is optional!" :)

Regards,
Jeff

Arnout Engelen <ar...@bz...> writes:

> I think a good out-of-the-box experience (i.e. good default settings)
> is hugely important. On the other hand, a stable, hassle-free upgrade
> path for existing users is equally essential.
>
> As an example, Dima recently contributed an option to only update the
> focuslist when a window has had the focus for some time
> ('focuslist_insert_delay'). We've left this feature 'off' by default in
> order not to affect existing users, but in fact this seems like something
> most users would benefit from.
>
> Is anyone aware of any applications that solve this tension gracefully?
> I.e. by prompting users on upgrade, perhaps telling them what changed and
> asking them whether they want to accept that change in their configuration?

I don't know of any ways to handle this on a distro-independent basis.
Since each distro handles installation and management of configuration
files differently, there likely isn't anything that "just works" for
everybody. This is a bit unsatisfying, but I think each distro
maintainer has to handle the announcement of potentially-breaking
changes themselves.

Debian has NEWS.Debian files to do this:

 https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-news-debian

We haven't yet released the new Debian packages with the changed
defaults, but we'll use this when we do.

For from-source installs, we should probably have a very loud
announcement in the CHANGELOG. We currently do mention the change in
that file, but it should probably be highlighted.

Anybody got better ideas?

dima

Hello,

I think a good out-of-the-box experience (i.e. good default settings) is
hugely important.
On the other hand, a stable, hassle-free upgrade path for existing users is
equally essential.

As an example, Dima recently contributed an option to only update the
focuslist when a window has had the focus for some time
('focuslist_insert_delay'). We've left this feature 'off' by default in
order not to affect existing users, but in fact this seems like something
most users would benefit from.

Is anyone aware of any applications that solve this tension gracefully?
I.e. by prompting users on upgrade, perhaps telling them what changed and
asking them whether they want to accept that change in their configuration?

I can imagine some interesting approaches, but would like to learn from
what others are already doing, too.

Kind regards,

Arnout

I'm uneasy with all the proposed keyboard changes.
Thus, as for my impression, I would just like to make sure nothing changes and that I can keep
my current layout even when notion as a whole gets update one day. So a solid way to switch 
whole layouts would be essential. Something like a query/menuitem  to change all layout.
This not only concerns the new, revolutionary change, but even the previous (like switching
Meta to "copyrightedlogo" key to which I find little excuse). 
Summarizing: whatever changes introduced, please make sure they're reversible. I believe people have
been using Ion/Notion for years and are quite adapted, so probably the keyboard hasn't been the problem for them/us.

Wojtek

On Wed, Jun 25, 2014 at 01:54:14PM -0700, Dima Kogan wrote:
> Arnout Engelen <no...@bz...> writes:
> 
> > I'd appreciate your thoughts on this approach. Details at
> > http://notion.sourceforge.net/notionkeys3.html .
> 
> Some thoughts in no particular order:
> 
> - This layout does not use the arrow keys at all. Those are a pretty
>   natural target for WM navigation, and I think they should be utilized.
>   The arrow keys could do the same things as some of your other bindings
>   to give the user a choice. As an example, I have
> 
>   - meta-left/right cycles tabs
>   - meta-up/down cycles workspaces
>   - meta-shift-left/right cycles screens
> 
> 
> - With your proposed bindings, how does one move objects between
>   containers? Specifically one should be able to move
> 
>   - windows between frames and
>   - workspaces between screens
> 
>   One way to do that is to tag/attach. In your proposed list I don't see
>   a way to move workspaces between screens; am I just not seeing it?
> 
> - In your reference page does "attract" mean "attach"?
> 
> - In your proposed bindings is meta-z same as meta-k k in the current
>   defaults? There needs to be some way to bring up the focuslist.
> 
> 
> Finally, it would be great to maintain some compatibility with other
> similar WMs. As far as I can tell, awesome is the current king of the
> hill, so how about we simply co-opt their defaults for our defaults?
> Their default bindings are here:
> 
>  http://awesome.naquadah.org/wiki/Awesome_3.x
> 
> Not all of our functions have analogues in their world, and vice versa,
> but for functions that do have analogues, I think we should match them.
> 
> dima
> 
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Notion-general mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-general

-- 
Wojtek Aniszewski
[Eng: voyteck aanishevsky]
[Fr:  vôytek anichévsky]

 /^..^\      ,-------------------------------------,
( (••) ) ----| My public GPG key ID: AC66485E      |
(|)_._(|)~   | please use email encryption!        |
             `-------------------------------------"
Web:   http://www.coria.fr/spip.php?auteur1606

Holger forgot to send this to the list, so I'm forwarding it here (with
his permission).

Holger Weiss <ho...@ze...> writes:

> On 25. Juni 2014 22:54:14 MESZ, Dima Kogan <no...@di...> wrote:
>>Finally, it would be great to maintain some compatibility with other
>>similar WMs. As far as I can tell, awesome is the current king of the
>>hill, so how about we simply co-opt their defaults for our defaults?
>
> I think i3 (http://i3wm.org/) is at least as successful these days,
> and more similar to Notion in some ways (e.g., built-in tabbing and
> manual layout management). So that might be an even better candidate
> for emulating keybindings?

Hi.

It doesn't look like i3 is quite as successful yet, but it's gaining:

http://qa.debian.org/popcon.php?package=i3-wm
http://qa.debian.org/popcon.php?package=awesome

I'm fine with imitating i3's bindings instead of awesome's. Just don't
want to see yet another "standard" pop up.

dima

Arnout Engelen <no...@bz...> writes:

> I'd appreciate your thoughts on this approach. Details at
> http://notion.sourceforge.net/notionkeys3.html .

Some thoughts in no particular order:

- This layout does not use the arrow keys at all. Those are a pretty
  natural target for WM navigation, and I think they should be utilized.
  The arrow keys could do the same things as some of your other bindings
  to give the user a choice. As an example, I have

  - meta-left/right cycles tabs
  - meta-up/down cycles workspaces
  - meta-shift-left/right cycles screens

- With your proposed bindings, how does one move objects between
  containers? Specifically one should be able to move

  - windows between frames and
  - workspaces between screens

  One way to do that is to tag/attach. In your proposed list I don't see
  a way to move workspaces between screens; am I just not seeing it?

- In your reference page does "attract" mean "attach"?

- In your proposed bindings is meta-z same as meta-k k in the current
  defaults? There needs to be some way to bring up the focuslist.

Finally, it would be great to maintain some compatibility with other
similar WMs. As far as I can tell, awesome is the current king of the
hill, so how about we simply co-opt their defaults for our defaults?
Their default bindings are here:

 http://awesome.naquadah.org/wiki/Awesome_3.x

Not all of our functions have analogues in their world, and vice versa,
but for functions that do have analogues, I think we should match them.

dima

Arnout Engelen <no...@bz...> writes:

> Thanks to many people involved, we now have a Notion branch with Xft
> support.

I built a .deb to ease testing for Debian users:

 http://pub.secretsauce.net/notion_3+2014052800-1xft1~1.gbpc742ad_amd64.deb

This should work on wheezy and sid; possibly Ubuntu as well, but I have
not checked.

The package sources live at https://github.com/dkogan/notion.xfttest

Note that the issue Arnout described earlier where xft disables
bitmapped fonts does exist on Debian boxes.

dima

Hello,

Thanks to many people involved, we now have a Notion branch with Xft
support.

If Xft support is detected at compile time, all font handling is done
through Xft, even for 'traditional' fonts: there should not need to be a
visible difference.

However, on some systems loading bitmap fonts through Xft is disabled.
Remove /etc/fonts/conf.d/70-no-bitmaps.conf to enable loading bitmap fonts
through fontconfig/Xft.

I'd like to invite all of you to test this branch and report any doubts you
may have about merging this patch into master. Get the code with:

$ git clone git://git.code.sf.net/p/notion/notion notion
$ cd notion
$ git branch xft remotes/origin/xft

Kind regards,

Arnout

Hi,

The current set of keybindings does not make much sense, and also claims
the function keys, which is inconvenient. I think it'd be useful to discuss
an overhaul.

I've put something together at
http://notion.sourceforge.net/notionkeys3.html .
I appreciate keybindings are something highly personal, so of course the
current bindings will remain available as an option and your custom
configuration will just keep working :). I do feel we should give new users
better defaults though.

The above attempt introduces 4 kinds of bindings:
1) Direct command keys: These take action immediately, i.e. splitting

2) Parameterized command keys: These open a query window for a parameter,
such as 'run'.

3) Locator keys. These identify a tab/frame/workspace/screen (absolutely or
relative to the currently focused). Pressing a locator key will move the
focus to that tab/frame/workspace/screen

4) Locator-parameterized command keys: These are commands that take a
tab/frame/workspace/screen parameter. When pressing such a command key:
* a query opens so you can search for the object by name
* a default is presented (so you can hopefully often just hit 'enter')
* you can alternatively specify the object by pressing the respective
locator keybinding

I'd appreciate your thoughts on this approach. Details at
http://notion.sourceforge.net/notionkeys3.html .

Kind regards,

Arnout

That did fix my problem.  I figured this out a while back, my apologies for
not following on on this thread to document it.

Thanks very much for following on despite the age of my question!

Jeff Abrahamson
+33 6 24 40 01 57   <-- briefly unavailable mid-June
+44 7920 594 255    <-- will change 18 July

http://jeff.purple.com/
http://blog.purple.com/jeff/

On 9 June 2014 22:58, Arnout Engelen <no...@bz...> wrote:

> On Sun, Feb 23, 2014 at 9:12 PM, Jeff Abrahamson <je...@pu...> wrote:
>
>> I'd like to push most of notion's key bindings into a submap under
>> META-tab.  Since the docs say to use the names in xkeysym.h (xkeysymdef.h),
>> I tried
>>
>> defbindings("WScreen", {
>>     submap(META..KB_Tab, {
>>
>>
>> and, since that didn't work,
>>
>> defbindings("WScreen", {
>>     submap(META..Tab, {
>>
>>
> Hi Jeff,
>
> Looks like this should be 'Tab' (I guess the docs could be improved there).
>
> I think the problem you're running into, though, is that "Tab" should be
> in quotes there. The error message is probably saying 'Tab' (which without
> quotes is a variable name) is 'nil'.
>
>
> Kind regards,
>
> Arnout
>

2010	Jan	Feb	Mar	Apr (2)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2011	Jan	Feb	Mar (3)	Apr (4)	May	Jun (4)	Jul	Aug (4)	Sep	Oct (20)	Nov (5)	Dec (5)
2012	Jan (37)	Feb (1)	Mar (5)	Apr (29)	May (3)	Jun (9)	Jul (6)	Aug (10)	Sep (16)	Oct (8)	Nov (9)	Dec (2)
2013	Jan (6)	Feb (6)	Mar	Apr	May	Jun (1)	Jul (4)	Aug (1)	Sep	Oct (6)	Nov (6)	Dec (1)
2014	Jan (1)	Feb (4)	Mar	Apr	May (16)	Jun (10)	Jul (8)	Aug (2)	Sep (2)	Oct	Nov	Dec
2015	Jan	Feb (1)	Mar	Apr	May (22)	Jun (22)	Jul (1)	Aug (8)	Sep (5)	Oct (2)	Nov (13)	Dec (2)
2016	Jan	Feb (5)	Mar	Apr	May	Jun (9)	Jul	Aug (2)	Sep (9)	Oct	Nov (2)	Dec (1)
2017	Jan	Feb (8)	Mar (1)	Apr	May (2)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2018	Jan	Feb	Mar	Apr	May (1)	Jun	Jul (4)	Aug (9)	Sep	Oct	Nov	Dec (1)
2019	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec

notion-general Mailing List for notion (Page 6)

Tabbed, tiling window manager.

notion-general — General discussion about the notion window manager