opening another terminal in FLuxbox makes it switch back to another desktop.

BW-userx · 01-15-2017, 02:31 PM

I've got Fluxbox running. If I already have a terminal running and move to another desktop then open up another terminal. It switches back to the desktop that has the first terminal open. even though it still opens up the other terminal in the desktop I was on. Making me have to switch back to that desktop. It is rather annoying.

Does any one know what 'config setting' perhaps in ~/.fluxbox/init needs to be written in to prevent it from doing that?

frankbell · 01-15-2017, 08:59 PM

I'm a long-time Fluxbox user and, I must say, I've not encountered that behavior on any OS on which I've used Fluxbox.

Have you tried opening a different terminal--say, if the first one is Xterm, move to the other desktop and open rxvt or gnome-terminal or something else? What happens in that case?

BW-userx · 01-16-2017, 05:57 AM

Quote:

Originally Posted by frankbell

I'm a long-time Fluxbox user and, I must say, I've not encountered that behavior on any OS on which I've used Fluxbox.

Me either until now. I am an on and off fluxbox user. xfce4 is my other WM I use but that was getting quirky so I switched back to Fluxbox and now this.

Quote:

Have you tried opening a different terminal--say, if the first one is Xterm, move to the other desktop and open rxvt or gnome-terminal or something else? What happens in that case?

well I open the same terminal - terminator - that is like my fav one.

keyboard shorts:

on say desktop 1 I open terminator then start a script then move to desktop 2 open another terminator (terminal) and it opens it up while jumping back to the desktop 1 where the first terminator - terminal running. I have to switch back to desktop 2 to get back to the second terminal I open so I can use that for whatever.

In gkrellm plugins

GKrellMLaunch (plugin)
Terminator launcher I get the same effects

The root menu off the desktop it does not do this. But that is not a fix and makes KB Shortcuts and plugin obsolete to just have to use the main menu.

( I just went through all of them right now to be sure)

Code:

[userx@voider.org]:
[~]>>$ fluxbox -v
Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox Team

I use menu maker for the menu.

Code:

mmaker -f fluxbox

right click on the title bar of an app.
On the menu item -> remember... menu items sub-menu
Jump to workspace
I do not have a full understanding of that that option does. Mostly because I cannot turn it off to see what that actually does.

It is highlighted and unable to be changed. Maybe that is what is causing it to jump back to the other workspace.

It seems to only be doing this with a terminal and no other applications.

I am going to add xterm to this and see if that gets the same results.

using the same method, opening up the same terminal in two different desktops.

xterm - it did not have the same effect.
xfce4-terminal - it did not have the same effect.

wtf - Why is it picking on the terminal I like to use?
I do not recall it ever doing this before.

This is not good. More investigation is now needed.

hazel · 01-16-2017, 08:06 AM

I would check the settings for terminator in ~/.fluxbox/apps. Maybe there's a workspace instruction there.

BW-userx · 01-16-2017, 08:16 AM

Quote:

Originally Posted by hazel

I would check the settings for terminator in ~/.fluxbox/apps. Maybe there's a workspace instruction there.

Their is just dimension settings for it in there.

does you or anyone know how to format that "Jump to workspace" in their config file? to turn it off. I cannot find anything on it other then it is on or off in the documentation I found on the net.

I am in Windows dealing with iTunes and mp3's right now. so ... No linux for a while

frankbell · 01-16-2017, 09:10 PM

I know this is no help, but I cannot duplicate this with Terminator in Fluxbox on Slackware --Current. I just opened one instance of Terminator on Desktop 4 and a separate instance on Desktop 1.

Here's my ~/.config/terminator/config file in case it yields a clue:

Code:

$ cat .config/terminator/config
[global_config]
  handle_size = 0
  inactive_color_offset = 0.74
[keybindings]
[profiles]
  [[default]]
    background_image = None
    background_darkness = 0.73
    scrollback_lines = 1500
    background_type = transparent
    scrollbar_position = left
    foreground_color = "#000000"
    font = Sans 20
    background_color = "#ffffff"
[layouts]
  [[default]]
    [[[child1]]]
      type = Terminal
      parent = window0
    [[[window0]]]
      type = Window
      parent = ""
[plugins]

My ~/.fluxbox/init file seems to have no reference to Terminator.

hazel · 01-17-2017, 12:49 AM

Quote:

Originally Posted by frankbell

My ~/.fluxbox/init file seems to have no reference to Terminator.

It wouldn't. init is the file that governs how fluxbox itself behaves. For information on how applications behave in fluxbox, you have to look at ~/.fluxbox/apps.

BW-userx · 01-17-2017, 08:48 AM

Quote:

Originally Posted by frankbell

I know this is no help, but I cannot duplicate this with Terminator in Fluxbox on Slackware --Current. I just opened one instance of Terminator on Desktop 4 and a separate instance on Desktop 1.

Here's my ~/.config/terminator/config file in case it yields a clue:

Code:

$ cat .config/terminator/config
[global_config]
  handle_size = 0
  inactive_color_offset = 0.74
[keybindings]
[profiles]
  [[default]]
    background_image = None
    background_darkness = 0.73
    scrollback_lines = 1500
    background_type = transparent
    scrollbar_position = left
    foreground_color = "#000000"
    font = Sans 20
    background_color = "#ffffff"
[layouts]
  [[default]]
    [[[child1]]]
      type = Terminal
      parent = window0
    [[[window0]]]
      type = Window
      parent = ""
[plugins]

My ~/.fluxbox/init file seems to have no reference to Terminator.

You are so right. I too cannot get Slackware to do this too.

I did discover this though while checking terminator versions between Slackware and Void;

in Slack I get this:

Code:

[userx@slacko]:
[~]>>$ fluxbox -v
Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox Team 

[userx@slacko]:
[~]>>$ terminator -v
terminator 0.98

In Void I get this:

Code:

    [userx@voider.org]:
    [~]>>$ fluxbox -v
    Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox Team 


    [userx@voider.org]:
    [~]>>$ terminator -v

    ** (process:1597): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

    ** (process:1597): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

    ** (process:1597): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
    terminator 1.0

I do not know if this GNOME warnings are causing this issue but I googled it and seen that it was reported way back in 2012, even in here to a Slackware maintainer (Patrick) that fixed it.

in LQ Slackware area:

[SOLVED] Python enum/GFlags WARNING

BW-userx · 01-17-2017, 08:52 AM

This is my config to Terminator

Code:

[global_config]
  focus = mouse
[keybindings]
[layouts]
  [[default]]
    [[[child1]]]
      parent = window0
      type = Terminal
    [[[window0]]]
      parent = ""
      type = Window
[plugins]
[profiles]
  [[default]]
    background_darkness = 0.9
    background_image = None
    background_type = transparent
    cursor_color = "#aaaaaa"
    login_shell = True
    scrollback_infinite = True

frankbell · 01-17-2017, 08:16 PM

My ~/.fluxbox/apps has no reference to Terminator. Here it is, for what it's worth:

Code:

~$ cat .fluxbox/apps
[app] (name=fbrun)
  [Position]	(CENTER)	{0 0}
  [Layer]	{2}
[end]
[app] (name=swisswatch) (class=SwissWatch)
  [Position]	(UPPERLEFT)	{91% -2%}
  [Sticky]	{yes}
  [Layer]	{10}
  [Close]	{yes}
[end]
[app] (name=gkrellm) (class=Gkrellm)
  [Layer]	{10}
  [Close]	{yes}
[end]
[app] (name=keepassx) (class=Keepassx)
[end]
[app] (name=XMMS_Player) (class=xmms)
  [Sticky]	{no}
  [Layer]	{8}
  [Close]	{yes}
[end]
[app] (name=pySol #2) (class=Pysol)
  [Position]	(UPPERLEFT)	{4% 2%}
[end]

BW-userx · 01-17-2017, 08:25 PM

Quote:

Originally Posted by frankbell

My ~/.fluxbox/apps has no reference to Terminator. Here it is, for what it's worth:

Code:

~$ cat .fluxbox/apps
[app] (name=fbrun)
  [Position]	(CENTER)	{0 0}
  [Layer]	{2}
[end]
[app] (name=swisswatch) (class=SwissWatch)
  [Position]	(UPPERLEFT)	{91% -2%}
  [Sticky]	{yes}
  [Layer]	{10}
  [Close]	{yes}
[end]
[app] (name=gkrellm) (class=Gkrellm)
  [Layer]	{10}
  [Close]	{yes}
[end]
[app] (name=keepassx) (class=Keepassx)
[end]
[app] (name=XMMS_Player) (class=xmms)
  [Sticky]	{no}
  [Layer]	{8}
  [Close]	{yes}
[end]
[app] (name=pySol #2) (class=Pysol)
  [Position]	(UPPERLEFT)	{4% 2%}
[end]

I'm begining to think it is some strange cross between VOID Linux and Terminator. because I think I've stated before, it does not do this in Slackware and they are sharing the same home directory using the same conf files.

frankbell · 01-17-2017, 08:45 PM

Quote:

it does not do this in Slackware and they are sharing the same home directory using the same conf files.

I have heard that strange things can happen when two distros try to use the same /home with the attendant config files. Never tried it myself.

BW-userx · 01-17-2017, 08:56 PM

Quote:

Originally Posted by frankbell

I have heard that strange things can happen when two distros try to use the same /home with their attendant config files. Never tried it myself.

I was hearing that too from others in here and else where. the ole don't be doing that. you're going to have problems, paranoia speach. But I wouldn't listen to it. Instead I found out myself.

The conflicts with different distros, Slack and Void play nice together, they are not all build up 'bloated' distros per se' whereas Debian and Void do not play nice together. I tried it. they just do not.

this thing I've experienced is if one of the distros you are using needs to use .xinit and the other one does not. Then using .xinit confuses the one that does not need it.

Fluxbox and xfce4 have thier own directories for config files, neither one needs the hidden files .xinit and share the one they do use. I have the same set up in my DE/WM just a different distro is all.

that why when I switch to the other one I am not using that ones KB shortcuts in the other one making mistakes because they are both 'cloned' DE/WM. because they both share the same config files.

the only real draw back would be if I have one distro with an app that the other one does not have. that is not a show stopper.

Benifts: when running the other DIstor I do not have to go into my other use home directory to get something making another copy of it, or having to move it over. it is already there.

UID needs to be the same that is not hard to do either.

hazel · 01-18-2017, 01:53 AM

Quote:

Originally Posted by BW-userx

that why when I switch to the other one I am not using that ones KB shortcuts in the other one making mistakes because they are both 'cloned' DE/WM. because they both share the same config files.

the only real draw back would be if I have one distro with an app that the other one does not have. that is not a show stopper.

Benifts: when running the other DIstor I do not have to go into my other use home directory to get something making another copy of it, or having to move it over. it is already there.

UID needs to be the same that is not hard to do either.

It's much simpler to reserve each of your home directories for distro-specific configuration files and keep your personal data on a "My Documents" partition that you can mount elsewhere. I mount mine on /home/data. That way, different distros' configuration files can't interfere with one another.

BW-userx · 01-18-2017, 08:23 AM

Quote:

Originally Posted by hazel

It's much simpler to reserve each of your home directories for distro-specific configuration files and keep your personal data on a "My Documents" partition that you can mount elsewhere. I mount mine on /home/data. That way, different distros' configuration files can't interfere with one another.

so you say and use the term "distro-specific configuration files" to justify what is in your belief system.

whereas I say "Window Manager specific configuration files" to justify what is in my belief system.

because each systems has its own little world to live in. they are on the system side. Whereas the user side has window managers and desktop managers conf files to deal with.

the two to not mesh they are separate. One should not keep all of the apache ssh ftp cron and other system config files in their home user directories for the system to have to go there to see what it is they are suppose to be doing. that is for the system side not user side.

it saves from having to move all of my extra stuff and put it in the shed outside of the house that I live. Why do that when I can have it right in the same house I live in instead?

Regardless of which door I go in to get into my House.

If I use firefox to download something it goes to Downloads, now I have to move it to /media/data for my other user account in my other distro so I can get at it from there instead by how you say I should/ I have to set up my system for whatever reasons that I see no real bases of truth to do so.

The way I have mine set up I eliminate that step and everything is still running copacetic.

system side. my one system auto mounts in Fluxbox, my other system does not. but that is not a WM/DE situation that is your "distro-specific configuration files" situation which has nothing to do with having both systems share the same user home.

making your way invalid.

think outside the box

Stop beveling everything someone else tells you, go and find out the truth for yourself. Put it to the test and see if it holds water or not.