Mac OS X - Revision history

Kjoonlee: /* Ventura Information */

2023-07-24T03:47:00Z

Ventura Information

← Older revision		Revision as of 03:47, 24 July 2023
Line 1:		Line 1:
	This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.		This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.

	== Ventura Information ==		== Ventura Information for 1.3 ==
			Inkscape 1.3 should be fine on macOS Ventura.

			== Ventura Information for 1.2.x ==

	If you’ve already updated to Ventura, try updating to Ventura 13.4 and see if mouse clicks work as intended.		If you’ve already updated to Ventura, try updating to Ventura 13.4 and see if mouse clicks work as intended.

Kjoonlee: /* Ventura Information */

2023-05-21T08:54:56Z

Ventura Information

← Older revision		Revision as of 08:54, 21 May 2023
Line 2:		Line 2:

	== Ventura Information ==		== Ventura Information ==

			If you’ve already updated to Ventura, try updating to Ventura 13.4 and see if mouse clicks work as intended.

			---

	Do not update to macOS Ventura if you rely on Inkscape! There is an unresolved issue that currently affects all GTK3 based apps on macOS Ventura, making the app unresponsive to certain mouse events. (GTK is used by many different programs, and builds those programs' user interfaces for you to interact with.)		Do not update to macOS Ventura if you rely on Inkscape! There is an unresolved issue that currently affects all GTK3 based apps on macOS Ventura, making the app unresponsive to certain mouse events. (GTK is used by many different programs, and builds those programs' user interfaces for you to interact with.)

Kjoonlee at 14:43, 6 December 2022

2022-12-06T14:43:12Z

← Older revision		Revision as of 14:43, 6 December 2022
Line 1:		Line 1:
	This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.		This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.

			== Ventura Information ==
			Do not update to macOS Ventura if you rely on Inkscape! There is an unresolved issue that currently affects all GTK3 based apps on macOS Ventura, making the app unresponsive to certain mouse events. (GTK is used by many different programs, and builds those programs' user interfaces for you to interact with.)

			Sample bugs:

			* https://gitlab.com/inkscape/inbox/-/issues/7798 Swatches (and other) menus not working in separate windows on MacOS Ventura
			* https://gitlab.com/inkscape/inbox/-/issues/7827 Font dropdown menu issues on MacOS Ventura
			* https://gitlab.com/inkscape/inbox/-/issues/7929 OSX Layers and Objects right mouse click is not triggered with CTRL + click

			Upstream bug:

			* https://gitlab.gnome.org/GNOME/gtk/-/issues/5305 widgets not reacting to mouse hover/click on macOS Ventura

	== Legacy Information ==		== Legacy Information ==

Kjoonlee at 15:56, 5 December 2022

2022-12-05T15:56:57Z

← Older revision		Revision as of 15:56, 5 December 2022
Line 1:		Line 1:
	This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.		This page is added as mini-TOC of Mac information on this Wiki, and a scratch pad for Mac stuff awaiting a home of its own.

	== Installing Inkscape ==		== Legacy Information ==
			=== Installing Inkscape ===

	Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. For 10.4.x users, X11 can be installed from your installation DVD. For 10.3.x users, you can get [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's X Server], or use [http://www.xdarwin.org/ XDarwin].		Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. For 10.4.x users, X11 can be installed from your installation DVD. For 10.3.x users, you can get [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's X Server], or use [http://www.xdarwin.org/ XDarwin].

Frigory: Frigory moved page MacOS X to Mac OS X: Separated words

2016-08-09T13:36:50Z

Frigory moved page MacOS X to Mac OS X: Separated words

← Older revision	Revision as of 13:36, 9 August 2016
(No difference)

Erlbeck: /* LaTex Specific Solution */Slight modification to match referenced document exactly.

2014-04-04T11:24:09Z

LaTex Specific Solution: Slight modification to match referenced document exactly.

← Older revision		Revision as of 11:24, 4 April 2014
Line 52:		Line 52:
	{inkscape -z -D --file=#1.svg %		{inkscape -z -D --file=#1.svg %
	--export-pdf=#1.pdf}%		--export-pdf=#1.pdf}%
	\~~includegraphics~~{#1.~~pdf~~}%		\input{#1.pdf_tex}%
	}		}
	to use the full Inkscape path. This is necessary when compiling LaTex through editors that don't see the aliases defined in `~/.profile`. The necessary preamble commands are then:		to use the full Inkscape path. This is necessary when compiling LaTex through editors that don't see the aliases defined in `~/.profile`. The necessary preamble commands are then:
Line 65:		Line 65:
	{/Applications/Inkscape.app/Contents/Resources/bin/inkscape -z -D --file=#1.svg %		{/Applications/Inkscape.app/Contents/Resources/bin/inkscape -z -D --file=#1.svg %
	--export-pdf=#1.pdf}%		--export-pdf=#1.pdf}%
	\~~includegraphics~~{#1.~~pdf~~}%		\input{#1.pdf_tex}%
	}		}

Erlbeck: /* Installing Inkscape */Added LaTex specific solution for invoking Inkscape from command line.

2014-04-02T11:27:54Z

Installing Inkscape: Added LaTex specific solution for invoking Inkscape from command line.

← Older revision		Revision as of 11:27, 2 April 2014
Line 39:		Line 39:
	You must reload your profile to see the changes:		You must reload your profile to see the changes:
	$ source ~/.profile		$ source ~/.profile

			=== LaTex Specific Solution ===
			For the specific case of updating the pdf and pdf_tex files from LaTex by invoking Inkscape from command line (see [http://distrib-coffee.ipsl.jussieu.fr/pub/mirrors/ctan/info/svg-inkscape/InkscapePDFLaTeX.pdf InkscapePDFLaTeX.pdf]), the easiest solution might be to alter the necessary LaTex preamble commands from:
			\newcommand{\executeiffilenewer}[3]{%
			\ifnum\pdfstrcmp{\pdffilemoddate{#1}}%
			{\pdffilemoddate{#2}}>0%
			{\immediate\write18{#3}}\fi%
			}

			\newcommand{\includesvg}[1]{%
			\executeiffilenewer{#1.svg}{#1.pdf}%
			{inkscape -z -D --file=#1.svg %
			--export-pdf=#1.pdf}%
			\includegraphics{#1.pdf}%
			}
			to use the full Inkscape path. This is necessary when compiling LaTex through editors that don't see the aliases defined in `~/.profile`. The necessary preamble commands are then:
			\newcommand{\executeiffilenewer}[3]{%
			\ifnum\pdfstrcmp{\pdffilemoddate{#1}}%
			{\pdffilemoddate{#2}}>0%
			{\immediate\write18{#3}}\fi%
			}

			\newcommand{\includesvg}[1]{%
			\executeiffilenewer{#1.svg}{#1.pdf}%
			{/Applications/Inkscape.app/Contents/Resources/bin/inkscape -z -D --file=#1.svg %
			--export-pdf=#1.pdf}%
			\includegraphics{#1.pdf}%
			}

	== See ==		== See ==

Markmfredrickson: Demonstrating my solution to the OS X command line problem: an alias

2011-08-14T19:15:45Z

Demonstrating my solution to the OS X command line problem: an alias

← Older revision		Revision as of 19:15, 14 August 2011
Line 32:		Line 32:
	$ /usr/local/bin/inkscape -z -D --file=image.svg --export-pdf=image.pdf --export-latex		$ /usr/local/bin/inkscape -z -D --file=image.svg --export-pdf=image.pdf --export-latex
	may not work because of a different interpretation of $0 and dirname. Tricky and unsolved in the general case...		may not work because of a different interpretation of $0 and dirname. Tricky and unsolved in the general case...

			=== Alias Solution ===

			The following can be added to your `~/.profile` file to create an alias that is expanded into the full Inkscape path:
			alias inkscape="/Applications/Inkscape.app/Contents/Resources/bin/inkscape"
			You must reload your profile to see the changes:
			$ source ~/.profile

	== See ==		== See ==

Revher: /* Inkscape command line */ Not as easy. It did not work any more as an App. I am confused about $0 in the script.

2011-04-05T18:01:28Z

Inkscape command line: Not as easy. It did not work any more as an App. I am confused about $0 in the script.

← Older revision		Revision as of 18:01, 5 April 2011
Line 21:		Line 21:
	But if you simply made a symbolic link to /usr/local/bin (which is in your PATH) with:		But if you simply made a symbolic link to /usr/local/bin (which is in your PATH) with:
	sudo ln -s /Applications/Inkscape.app/Contents/Resources/bin/inkscape /usr/local/bin		sudo ln -s /Applications/Inkscape.app/Contents/Resources/bin/inkscape /usr/local/bin
	the command invoked by the default Inkscape script:		the command invoked by the default Inkscape script (0.48.1):
	$ dirname $0		$ dirname $0
	~~will~~ not move to Inkscape's Resources directory but to /usr/local/bin.		might not move to Inkscape's Resources directory but to /usr/local/bin.
	~~A command like:~~
	~~$ dirname $(readlink $0)~~
	~~seems working~~.

	~~Waiting for better solutions~~, ~~you can try the following change in the file~~ /~~Applications~~/~~Inkscape~~.~~app~~/~~Contents~~/~~Resources~~/bin/inkscape (0.48.~~1):~~		From a terminal, even if
			$ which inkscape
	~~#CWD="`(cd \"\`dirname \\\"~~$0~~\\\"\`\"; echo \"$PWD\")`"~~		refers to /usr/local/bin/inkscape, a command like:
	~~CWD="`(cd \"\`~~dirname ~~$(readlink \\\"$0\\\")\`\"; echo \"$PWD\")`"~~		$ inkscape -z -D --file=image.svg --export-pdf=image.pdf --export-latex
			may work while:
			$ /usr/local/bin/inkscape -z -D --file=image.svg --export-pdf=image.pdf --export-latex
			may not work because of a different interpretation of $0 and dirname. Tricky and unsolved in the general case...

	== See ==		== See ==

Revher: /* Installing Inkscape */ Command line?

2011-04-05T15:04:56Z

Installing Inkscape: Command line?

← Older revision		Revision as of 15:04, 5 April 2011
Line 10:		Line 10:

	Otherwise start Inkscape by double clicking one of its documents and it will thereafter be available to you in the Dock and from the "Recent Items" menu-item.		Otherwise start Inkscape by double clicking one of its documents and it will thereafter be available to you in the Dock and from the "Recent Items" menu-item.

			====Inkscape command line ====
			For many purposes you may need to execute Inkscape from the command line. For example within a LaTeX document you can update the pdf and pdf_tex files with your maths with the following command (see [http://distrib-coffee.ipsl.jussieu.fr/pub/mirrors/ctan/info/svg-inkscape/InkscapePDFLaTeX.pdf InkscapePDFLaTeX.pdf]):
			inkscape -z -D --file=image.svg --export-pdf=image.pdf --export-latex

			The Inkscape script is supposed to change to Inkscape's Resources directory
			cd /Applications/Inkscape.app/Contents/Resources/bin
			in order to get the correct environments for Inkscape as well as for native (Apple) Python.

			But if you simply made a symbolic link to /usr/local/bin (which is in your PATH) with:
			sudo ln -s /Applications/Inkscape.app/Contents/Resources/bin/inkscape /usr/local/bin
			the command invoked by the default Inkscape script:
			$ dirname $0
			will not move to Inkscape's Resources directory but to /usr/local/bin.
			A command like:
			$ dirname $(readlink $0)
			seems working.

			Waiting for better solutions, you can try the following change in the file /Applications/Inkscape.app/Contents/Resources/bin/inkscape (0.48.1):

			#CWD="`(cd \"\`dirname \\\"$0\\\"\`\"; echo \"$PWD\")`"
			CWD="`(cd \"\`dirname $(readlink \\\"$0\\\")\`\"; echo \"$PWD\")`"

	== See ==		== See ==