New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xmind not accept command line parameters? #200

Closed
GoogleCodeExporter opened this Issue Mar 19, 2015 · 16 comments

Comments

Projects
None yet
3 participants
@GoogleCodeExporter

GoogleCodeExporter commented Mar 19, 2015

What steps will reproduce the problem?
1. try to execute "xmind file.xmind" in the shell 

What is the expected output? What do you see instead?
To open file.xmind opened into the xmind program, instead, it opens xmind with 
new map.

What version of the product are you using? On what operating system?
version 3.1.1 in Linux

Please provide any additional information below.
Well, I tried to create a mime type to xmind in gnome, so I can just click in 
.xmind files and open into the xmind directly. But, xmind just won't accept 
command line argument so the mime type created will not work. The result is 
that when click on the .xmind file, xmind just open a new map instead of the 
file.

Original issue reported on code.google.com by ricardo....@gmail.com on 25 Aug 2010 at 5:40

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

I have the same issue on Linux (Ubuntu 64) w/3.2.0.

Original comment by brect...@gmail.com on 17 Sep 2010 at 4:47

GoogleCodeExporter commented Mar 19, 2015

I have the same issue on Linux (Ubuntu 64) w/3.2.0.

Original comment by brect...@gmail.com on 17 Sep 2010 at 4:47

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

we still have not found a solution to open an exiting .xmind file via 
double-click on Ubuntu. 

Original comment by stephen0...@gmail.com on 7 Oct 2010 at 6:49

  • Changed state: Accepted

GoogleCodeExporter commented Mar 19, 2015

we still have not found a solution to open an exiting .xmind file via 
double-click on Ubuntu. 

Original comment by stephen0...@gmail.com on 7 Oct 2010 at 6:49

  • Changed state: Accepted
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

subscribing (having the same issue)

Original comment by wouter...@gmail.com on 2 Nov 2010 at 2:38

GoogleCodeExporter commented Mar 19, 2015

subscribing (having the same issue)

Original comment by wouter...@gmail.com on 2 Nov 2010 at 2:38

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

Hi,

after having this problem in Ubuntu 10.04 and xmind-portable 3.2.1 I did some 
testing. 

First thing I noticed is, if I try to open a xmind file with a double click and 
use the xmind binary as target, xmind opens an shows an empty workspace.

When I use the xmind-bin file as target, xmind crashes with an exception. This 
is, because the application isn't run from its home directory.

So what I did as a workaround: I wrote a little shell script, that changes to 
the xmind directory before executing xmind-bin:

#!/bin/bash
cd /home/user/software/xmind-portable-3.2.1.201011212218/XMind_Linux
./xmind-bin $1

When I use my script as a target for opening xmind files, the mind map opens.

Unfortunately there is still one thing that is a bit annoying. The mind map I 
try to open by double click is loaded, but there is also loaded an empty mind 
map in the foreground. So you have to switch to the other tab to get your xmind 
file.

Maybe this helps someone... It would be great if this feature can be added in a 
future version.

Original comment by alexande...@gmail.com on 23 Nov 2010 at 8:02

GoogleCodeExporter commented Mar 19, 2015

Hi,

after having this problem in Ubuntu 10.04 and xmind-portable 3.2.1 I did some 
testing. 

First thing I noticed is, if I try to open a xmind file with a double click and 
use the xmind binary as target, xmind opens an shows an empty workspace.

When I use the xmind-bin file as target, xmind crashes with an exception. This 
is, because the application isn't run from its home directory.

So what I did as a workaround: I wrote a little shell script, that changes to 
the xmind directory before executing xmind-bin:

#!/bin/bash
cd /home/user/software/xmind-portable-3.2.1.201011212218/XMind_Linux
./xmind-bin $1

When I use my script as a target for opening xmind files, the mind map opens.

Unfortunately there is still one thing that is a bit annoying. The mind map I 
try to open by double click is loaded, but there is also loaded an empty mind 
map in the foreground. So you have to switch to the other tab to get your xmind 
file.

Maybe this helps someone... It would be great if this feature can be added in a 
future version.

Original comment by alexande...@gmail.com on 23 Nov 2010 at 8:02

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015


Another problem I just ran into with my shell script: When xmind is already 
running and I try to open a second file via the file manager, another instance 
of xmind is started complaining about a previous crash.

If I run the xmind binary (not xmind-bin) twice, it's the same. I get two 
running xminds. The only difference to running xmind-bin twice is, that I don't 
get an error about a previous crash.

On windows xmind detects that there is already an instance running and just 
opens the new file which is the behavior I would expect.

Original comment by alexande...@gmail.com on 20 Jan 2011 at 7:13

GoogleCodeExporter commented Mar 19, 2015


Another problem I just ran into with my shell script: When xmind is already 
running and I try to open a second file via the file manager, another instance 
of xmind is started complaining about a previous crash.

If I run the xmind binary (not xmind-bin) twice, it's the same. I get two 
running xminds. The only difference to running xmind-bin twice is, that I don't 
get an error about a previous crash.

On windows xmind detects that there is already an instance running and just 
opens the new file which is the behavior I would expect.

Original comment by alexande...@gmail.com on 20 Jan 2011 at 7:13

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

I'm still facing this problem.

Any plans to fix this?

My .desktop file:


[root@funkenote ~]# cat /usr/share/applications/xmind.desktop 
[Desktop Entry]
Encoding=UTF-8
Name=XMind
Comment=Launch XMind 3.0
Exec=/usr/bin/xmind %f
Terminal=false
Type=Application
Icon=xmind.png
StartupNotify=true
Categories=Office;
MimeType=application/xmind;

Thanks

Original comment by ricardo....@gmail.com on 30 Jul 2011 at 7:07

GoogleCodeExporter commented Mar 19, 2015

I'm still facing this problem.

Any plans to fix this?

My .desktop file:


[root@funkenote ~]# cat /usr/share/applications/xmind.desktop 
[Desktop Entry]
Encoding=UTF-8
Name=XMind
Comment=Launch XMind 3.0
Exec=/usr/bin/xmind %f
Terminal=false
Type=Application
Icon=xmind.png
StartupNotify=true
Categories=Office;
MimeType=application/xmind;

Thanks

Original comment by ricardo....@gmail.com on 30 Jul 2011 at 7:07

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

I just found this because I was having a similar issue. xmind and xmind-bin 
both appear to ignore the command-line arguments, breaking any type of shell 
integration. To the end user it appears to load a blank document when an 
existing document was specified. In my .deb package, there is no apparent 
work-around.

Original comment by jshook on 17 Aug 2011 at 6:28

GoogleCodeExporter commented Mar 19, 2015

I just found this because I was having a similar issue. xmind and xmind-bin 
both appear to ignore the command-line arguments, breaking any type of shell 
integration. To the end user it appears to load a blank document when an 
existing document was specified. In my .deb package, there is no apparent 
work-around.

Original comment by jshook on 17 Aug 2011 at 6:28

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

I just found this because I was having a similar issue. xmind and xmind-bin 
both appear to ignore the command-line arguments, breaking any type of shell 
integration. To the end user it appears to load a blank document when an 
existing document was specified. In my .deb package, there is no apparent 
work-around.

Original comment by jshook on 17 Aug 2011 at 6:45

GoogleCodeExporter commented Mar 19, 2015

I just found this because I was having a similar issue. xmind and xmind-bin 
both appear to ignore the command-line arguments, breaking any type of shell 
integration. To the end user it appears to load a blank document when an 
existing document was specified. In my .deb package, there is no apparent 
work-around.

Original comment by jshook on 17 Aug 2011 at 6:45

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

Same problem of empty map and shell integration.
Concerning shell integration, the *.xmind files have a zip file type ; they 
should be identified by an "xmind" magic number. Then I could link the 
xmind-bin program to this xmind file type. Best regards,

Original comment by EricFe...@scarlet.be on 9 Sep 2011 at 12:38

GoogleCodeExporter commented Mar 19, 2015

Same problem of empty map and shell integration.
Concerning shell integration, the *.xmind files have a zip file type ; they 
should be identified by an "xmind" magic number. Then I could link the 
xmind-bin program to this xmind file type. Best regards,

Original comment by EricFe...@scarlet.be on 9 Sep 2011 at 12:38

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

With xmind-bin it works here, but I wish to know the differences between xmind 
and xmind-bin...

Original comment by ricardo....@gmail.com on 9 Sep 2011 at 5:47

GoogleCodeExporter commented Mar 19, 2015

With xmind-bin it works here, but I wish to know the differences between xmind 
and xmind-bin...

Original comment by ricardo....@gmail.com on 9 Sep 2011 at 5:47

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

Same problem using the last version of XMind. I already reported it (facebook, 
email). I don't know if they have any plans to fix it. Does it work in windows? 
In my experience, handling cli args in linux and win is not very different, but 
I may be missing something. I haven't checked the code (it used to work in 
previous versions), so I don't know if support is missing in the linux version 
or if it's just a bug. If anyone could take a peek, we'd all be very grateful.

Original comment by ivanpere...@gmail.com on 11 Dec 2011 at 3:27

GoogleCodeExporter commented Mar 19, 2015

Same problem using the last version of XMind. I already reported it (facebook, 
email). I don't know if they have any plans to fix it. Does it work in windows? 
In my experience, handling cli args in linux and win is not very different, but 
I may be missing something. I haven't checked the code (it used to work in 
previous versions), so I don't know if support is missing in the linux version 
or if it's just a bug. If anyone could take a peek, we'd all be very grateful.

Original comment by ivanpere...@gmail.com on 11 Dec 2011 at 3:27

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

[deleted comment]

GoogleCodeExporter commented Mar 19, 2015

[deleted comment]
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015

I've just downloaded debian package 3.3.0 ; I did not found a way to handle 
correctly command line arguments with this version.

using advises 6 from Ricardo help me having xmind working nice : just "cd" to 
the install directory before running xmind application.

Original comment by mquin...@gmail.com on 6 Sep 2012 at 5:22

GoogleCodeExporter commented Mar 19, 2015

I've just downloaded debian package 3.3.0 ; I did not found a way to handle 
correctly command line arguments with this version.

using advises 6 from Ricardo help me having xmind working nice : just "cd" to 
the install directory before running xmind application.

Original comment by mquin...@gmail.com on 6 Sep 2012 at 5:22

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 19, 2015


The behavior is now better in XMind 3.3.0.

For the portable version (on Linux) I still need to use a bash script to change 
the directory before starting, but opening files now works as expected.

I attached the shell script, that I'm currently using.

Original comment by alexande...@gmail.com on 9 Nov 2012 at 10:36

Attachments:

GoogleCodeExporter commented Mar 19, 2015


The behavior is now better in XMind 3.3.0.

For the portable version (on Linux) I still need to use a bash script to change 
the directory before starting, but opening files now works as expected.

I attached the shell script, that I'm currently using.

Original comment by alexande...@gmail.com on 9 Nov 2012 at 10:36

Attachments:

@ivanperez-keera

This comment has been minimized.

Show comment
Hide comment
@ivanperez-keera

ivanperez-keera Jul 8, 2017

Possible duplicate #196 .

ivanperez-keera commented Jul 8, 2017

Possible duplicate #196 .

@frankshaka

This comment has been minimized.

Show comment
Hide comment
@frankshaka

frankshaka Oct 19, 2017

Member

Closing this issue as it is too old.

Member

frankshaka commented Oct 19, 2017

Closing this issue as it is too old.

@frankshaka frankshaka closed this Oct 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment