Bug 354898 - kile does not seem to implement kate color schema and syntaxhighlighting
Summary: kile does not seem to implement kate color schema and syntaxhighlighting
Status: REPORTED
Alias: None
Product: kile
Classification: Applications
Component: editor (other bugs)
Version First Reported In: 2.1.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-05 14:24 UTC by R (Chandra) Chandrasekhar
Modified: 2021-03-09 06:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R (Chandra) Chandrasekhar 2015-11-05 14:24:49 UTC
I am on Netrunner Rolling 2015-09 running Plasma 5, KDE Frameworks 5.15.0, kate 15.08.2, and kile 2.1.3.

In the past, when I added a schema and syntaxhighlighting to kate, it was automatically reflected in kile as well. Examples include zenburn, DarkOxygen, Oblivion, etc.

It is no more so now.

How might I restore the previous behaviour?

Reproducible: Always

Steps to Reproduce:
1. Choose a schema: e.g., zenburn
2. Add the schema and syntaxhighlighting files to $HOME/.config/kateschemarc and katesyntaxhighlightingrc.
3. Confirm that they appear as options in the settings for kate.
4. Check whether they appear as options for settings for kile.
5. If not, reboot and check again.

Actual Results:  
The options appeared for kate but not for kile.

Expected Results:  
The options should appear for kile as well as kate.

zenburn is available at:

http://kde-apps.org/content/show.php/Zenburn+Theme+for+Kate+highlighting?content=144674

Note that in Netrunner, the schema and syntax-highlighting files should be installed in $HOME/.config
Comment 1 Justin Zobel 2021-03-09 06:59:11 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.