[SOLVED] How do I get Mousepad to do syntax colouring?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I wanted to add mousepad to my Slackware 14.2 system, so I got it from SlackBuilds.org.
Mousepad requires gtksourceview3, so I got that, too.
Gtksourceview3, in turn, requires glade, so I got that as well.
Then I built glade, which gave me ‘glade-3.18.3-x86_64-1_SBo.tgz’.
I used ‘installpkg’ to install the package, without any errors.
Next, I built gtksourceview3, which gave me ‘gtksourceview3-3.18.4-x86_64-1_SBo.tgz’.
Again, I used ‘installpkg’ to install the package, without any errors.
And finally, I built mousepad, which gave me ‘mousepad-0.4.1-x86_64-1_SBo.tgz’.
Once more, I used ‘installpkg’ to install the package, without any errors.
Mousepad works fine, except that it doesn’t do syntax colouring. It does correctly identify the file type—so, e.g., when I load a ‘*.c’ file, then “Document” ⇒ “Filetype” ⇒ “Source” ⇒ “C” is selected. The ‘*.lang’ files (including ‘c.lang’) are present in the ‘/usr/share/gtksourceview-3.0/language-specs’ directory.
I went looking for some ‘configure’ option that might be needed to make mousepad activate syntax highlighting, but I didn’t find anything that rang a bell.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
Quote:
Originally Posted by luvr
I wanted to add mousepad to my Slackware 14.2 system, so I got it from SlackBuilds.org.
Mousepad requires gtksourceview3, so I got that, too.
Gtksourceview3, in turn, requires glade, so I got that as well.
Then I built glade, which gave me ‘glade-3.18.3-x86_64-1_SBo.tgz’.
I used ‘installpkg’ to install the package, without any errors.
Next, I built [I]gtksourceview3,[/ I] which gave me ‘gtksourceview3-3.18.4-x86_64-1_SBo.tgz’.
Again, I used ‘installpkg’ to install the package, without any errors.
And finally, I built mousepad, which gave me ‘mousepad-0.4.1-x86_64-1_SBo.tgz’.
Once more, I used ‘installpkg’ to install the package, without any errors.
I think you didn't install with sbopkg, it worth a look https://www.sbopkg.org/
It has 'sqg' that builds a queue file with all dependencies for SlackBuilds, then
with a command like 'sbopkg -R -k -i mousepad', sbopkg will ask if you want install
the queue or just the package.
Quote:
Mousepad works fine, except that it doesn’t do syntax colouring. It does correctly identify the file type—so, e.g., when I load a ‘*.c’ file, then “Document” ⇒ “Filetype” ⇒ “Source” ⇒ “C” is selected. The ‘*.lang’ files (including ‘c.lang’) are present in the ‘/usr/share/gtksourceview-3.0/language-specs’ directory.
I went looking for some ‘configure’ option that might be needed to make mousepad activate syntax highlighting, but I didn’t find anything that rang a bell.
Turned out that syntax colouring did work after all... Only silly little detail was the Colour scheme (on the “Edit” ⇒ “Preferences” dialogue) which was set to... “None”. I set it to “Classic” instead, et voilà: syntax colouring instantly showed up.
I had seen that thread, but considered it not applicable, since it discussed a different issue, where syntax colouring did visibly work, but the user wanted to add file type “*.SlackBuild” to be handled just like a shell script. Rereading the thread now that I have syntax colouring working, I thought that was a great idea, so now my SlackBuilds are nicely coloured as well.
So, no it didn’t help, but yes, it did help after all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.