Customising markdown syntax highlighting in GeanyBash syntax highlighting of subshellsSyntax highlighting of...
How to pass query parameters in URL in Salesforce Summer 19 Release?
Is throwing dice a stochastic or a deterministic process?
What happens if I accidentally leave an app running and click "Install Now" in Software Updater?
Meaning of the (idiomatic?) expression "seghe mentali"
Drawing an hexagonal cone in TikZ 2D
Has the United States ever had a non-Christian President?
What do you call a painting on a wall?
The origin of list data structure
Understanding ties
Sparring against two opponents test
Install Firefox without updates
Where are the "shires" in the UK?
Madam I m Adam..please don’t get mad..you will no longer be prime
What is the closest airport to the center of the city it serves?
Krull dimension of the ring of global sections
How can a hefty sand storm happen in a thin atmosphere like Martian?
Dirichlet series with a single zero
Why are the capacitors necessary for a quartz crystal?
What is a common way to tell if an academic is "above average," or outstanding in their field? Is their h-index (Hirsh index) one of them?
How to calculate rate of axial precession?
The Adventures of a Chocolate Cookie
What happens to the electronic movements at absolute 0?
Which US defense organization would respond to an invasion like this?
Would a "Permanence" spell in 5e be overpowered?
Customising markdown syntax highlighting in Geany
Bash syntax highlighting of subshellsSyntax highlighting of latex code blocks in ikiwikiless command and syntax highlightingAsciiDoc syntax highlighting plugin for Kate?Joe's own editor: changing syntax highlightingVim syntax highlighting fails with autosessionSyntax highlighting and export EPUB format.jsf syntax highlighting file (for joe editor)Syntax highlighting in the terminalExtend syntax highlighting for Markdown in Kate?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm using Geany 1.23.1 on Lubuntu 13.10.
I've copied over filetypes.markdown from /usr/share/geany to ~/.config/geany/filedefs.
filetypes.markdown has the following content:
# For complete documentation of this file, please see Geany's main documentation
[styling]
# Edit these in the colorscheme .conf file instead
default=default
strong=string_3
emphasis=string_4
header1=keyword_1
header2=keyword_1
header3=keyword_1
header4=keyword_1
header5=keyword_1
header6=keyword_1
ulist_item=tag_unknown
olist_item=tag_unknown
blockquote=tag_unknown
strikeout=tag_unknown
hrule=tag_unknown
link=keyword_1
code=attribute_unknown
codebk=attribute_unknown
[settings]
# default extension used when saving files
extension=mkd
# sort tags by appearance
symbol_list_sort_mode=1
Why is the third line present: # Edit these in the colorscheme .conf file instead?
What is wrong with editing filetypes.markdown itself? I would think that, at least from a user's perspective, editing ~/.config/geany/filedefs/filetypes.markdown (or any other filetypes file) would be preferable to editing a .conf file (in ~/.config/geany/colorschemes) as suggested because editing a .conf file would affect all filetypes not just filetype.markdown.
syntax-highlighting markdown geany
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm using Geany 1.23.1 on Lubuntu 13.10.
I've copied over filetypes.markdown from /usr/share/geany to ~/.config/geany/filedefs.
filetypes.markdown has the following content:
# For complete documentation of this file, please see Geany's main documentation
[styling]
# Edit these in the colorscheme .conf file instead
default=default
strong=string_3
emphasis=string_4
header1=keyword_1
header2=keyword_1
header3=keyword_1
header4=keyword_1
header5=keyword_1
header6=keyword_1
ulist_item=tag_unknown
olist_item=tag_unknown
blockquote=tag_unknown
strikeout=tag_unknown
hrule=tag_unknown
link=keyword_1
code=attribute_unknown
codebk=attribute_unknown
[settings]
# default extension used when saving files
extension=mkd
# sort tags by appearance
symbol_list_sort_mode=1
Why is the third line present: # Edit these in the colorscheme .conf file instead?
What is wrong with editing filetypes.markdown itself? I would think that, at least from a user's perspective, editing ~/.config/geany/filedefs/filetypes.markdown (or any other filetypes file) would be preferable to editing a .conf file (in ~/.config/geany/colorschemes) as suggested because editing a .conf file would affect all filetypes not just filetype.markdown.
syntax-highlighting markdown geany
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The originalfiletype.markdownhas "code=attribute_unknown". Then I look at the appropriate.confin~/.config/geany/colorschemes(Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".
– user15760
Oct 30 '13 at 4:35
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply editfiletypes.markdownin my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.
– user15760
Oct 30 '13 at 4:39
add a comment |
I'm using Geany 1.23.1 on Lubuntu 13.10.
I've copied over filetypes.markdown from /usr/share/geany to ~/.config/geany/filedefs.
filetypes.markdown has the following content:
# For complete documentation of this file, please see Geany's main documentation
[styling]
# Edit these in the colorscheme .conf file instead
default=default
strong=string_3
emphasis=string_4
header1=keyword_1
header2=keyword_1
header3=keyword_1
header4=keyword_1
header5=keyword_1
header6=keyword_1
ulist_item=tag_unknown
olist_item=tag_unknown
blockquote=tag_unknown
strikeout=tag_unknown
hrule=tag_unknown
link=keyword_1
code=attribute_unknown
codebk=attribute_unknown
[settings]
# default extension used when saving files
extension=mkd
# sort tags by appearance
symbol_list_sort_mode=1
Why is the third line present: # Edit these in the colorscheme .conf file instead?
What is wrong with editing filetypes.markdown itself? I would think that, at least from a user's perspective, editing ~/.config/geany/filedefs/filetypes.markdown (or any other filetypes file) would be preferable to editing a .conf file (in ~/.config/geany/colorschemes) as suggested because editing a .conf file would affect all filetypes not just filetype.markdown.
syntax-highlighting markdown geany
I'm using Geany 1.23.1 on Lubuntu 13.10.
I've copied over filetypes.markdown from /usr/share/geany to ~/.config/geany/filedefs.
filetypes.markdown has the following content:
# For complete documentation of this file, please see Geany's main documentation
[styling]
# Edit these in the colorscheme .conf file instead
default=default
strong=string_3
emphasis=string_4
header1=keyword_1
header2=keyword_1
header3=keyword_1
header4=keyword_1
header5=keyword_1
header6=keyword_1
ulist_item=tag_unknown
olist_item=tag_unknown
blockquote=tag_unknown
strikeout=tag_unknown
hrule=tag_unknown
link=keyword_1
code=attribute_unknown
codebk=attribute_unknown
[settings]
# default extension used when saving files
extension=mkd
# sort tags by appearance
symbol_list_sort_mode=1
Why is the third line present: # Edit these in the colorscheme .conf file instead?
What is wrong with editing filetypes.markdown itself? I would think that, at least from a user's perspective, editing ~/.config/geany/filedefs/filetypes.markdown (or any other filetypes file) would be preferable to editing a .conf file (in ~/.config/geany/colorschemes) as suggested because editing a .conf file would affect all filetypes not just filetype.markdown.
syntax-highlighting markdown geany
syntax-highlighting markdown geany
asked Oct 30 '13 at 3:44
user15760
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The originalfiletype.markdownhas "code=attribute_unknown". Then I look at the appropriate.confin~/.config/geany/colorschemes(Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".
– user15760
Oct 30 '13 at 4:35
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply editfiletypes.markdownin my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.
– user15760
Oct 30 '13 at 4:39
add a comment |
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The originalfiletype.markdownhas "code=attribute_unknown". Then I look at the appropriate.confin~/.config/geany/colorschemes(Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".
– user15760
Oct 30 '13 at 4:35
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply editfiletypes.markdownin my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.
– user15760
Oct 30 '13 at 4:39
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The original
filetype.markdown has "code=attribute_unknown". Then I look at the appropriate .conf in ~/.config/geany/colorschemes (Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".– user15760
Oct 30 '13 at 4:35
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The original
filetype.markdown has "code=attribute_unknown". Then I look at the appropriate .conf in ~/.config/geany/colorschemes (Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".– user15760
Oct 30 '13 at 4:35
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply edit
filetypes.markdown in my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.– user15760
Oct 30 '13 at 4:39
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply edit
filetypes.markdown in my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.– user15760
Oct 30 '13 at 4:39
add a comment |
1 Answer
1
active
oldest
votes
The filetypes.* configuration are overriding styling rules defined in colorschemes files.
In your personal filetypes.* configuration, if you use a common named_style (they are in [named_styles] section of colorschemes files), you override this style and when you change colorscheme, you may have unexpected results.
If you create a personal named_style, you override nothing but you have to add it in each colorschemes to ensure that the visual result is compatible with it.
See Geany's documentation
Filetype configuration:
- [styling] section
- [named_styles] section
- Color schemes
answered Jun 11 '18 at 8:33
freezedfreezed
1367
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f98157%2fcustomising-markdown-syntax-highlighting-in-geany%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The filetypes.* configuration are overriding styling rules defined in colorschemes files.
In your personal filetypes.* configuration, if you use a common named_style (they are in [named_styles] section of colorschemes files), you override this style and when you change colorscheme, you may have unexpected results.
If you create a personal named_style, you override nothing but you have to add it in each colorschemes to ensure that the visual result is compatible with it.
See Geany's documentation
Filetype configuration:
- [styling] section
- [named_styles] section
- Color schemes
answered Jun 11 '18 at 8:33
freezedfreezed
1367
add a comment |
The filetypes.* configuration are overriding styling rules defined in colorschemes files.
In your personal filetypes.* configuration, if you use a common named_style (they are in [named_styles] section of colorschemes files), you override this style and when you change colorscheme, you may have unexpected results.
If you create a personal named_style, you override nothing but you have to add it in each colorschemes to ensure that the visual result is compatible with it.
See Geany's documentation
Filetype configuration:
- [styling] section
- [named_styles] section
- Color schemes
answered Jun 11 '18 at 8:33
freezedfreezed
1367
add a comment |
The filetypes.* configuration are overriding styling rules defined in colorschemes files.
In your personal filetypes.* configuration, if you use a common named_style (they are in [named_styles] section of colorschemes files), you override this style and when you change colorscheme, you may have unexpected results.
If you create a personal named_style, you override nothing but you have to add it in each colorschemes to ensure that the visual result is compatible with it.
See Geany's documentation
Filetype configuration:
- [styling] section
- [named_styles] section
- Color schemes
answered Jun 11 '18 at 8:33
freezedfreezed
1367
The filetypes.* configuration are overriding styling rules defined in colorschemes files.
In your personal filetypes.* configuration, if you use a common named_style (they are in [named_styles] section of colorschemes files), you override this style and when you change colorscheme, you may have unexpected results.
If you create a personal named_style, you override nothing but you have to add it in each colorschemes to ensure that the visual result is compatible with it.
See Geany's documentation
Filetype configuration:
- [styling] section
- [named_styles] section
- Color schemes
answered Jun 11 '18 at 8:33
freezedfreezed
1367
answered Jun 11 '18 at 8:33
freezedfreezed
1367
answered Jun 11 '18 at 8:33
freezedfreezed
1367
answered Jun 11 '18 at 8:33
freezedfreezed
1367
1367
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f98157%2fcustomising-markdown-syntax-highlighting-in-geany%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Total guess but is it one of those situations where the filetypes.markdown can be managed by a package, and customizations are kept in a separate file?
– slm♦
Oct 30 '13 at 3:59
I've just begun getting used to using Geany. I try to read the manual for help first but I couldn't get my doubt cleared up. Just as an example, we use ` and ` to enclose inline code in markdown. The original
filetype.markdownhas "code=attribute_unknown". Then I look at the appropriate.confin~/.config/geany/colorschemes(Dark Solarized theme for geany: ethanschoonover.com/solarized) and see "attribute_unknown=attribute,bold" and "attribute=keyword_1" and "keyword_1=keyword" and "keyword=#0086b3;;true".– user15760
Oct 30 '13 at 4:35
@slm My point is that if I edit the theme's .conf to change "keyword=#0086b3;;true" to something else, all other file types, html, css, js, py, will have the changed keyword. Whereas, I can simply edit
filetypes.markdownin my home and not affect any other file type's appearance. Which I why I'm trying to understand the comment line I referred to in my question. Editing filetypes.markdown doesn't seem to break anything so far.– user15760
Oct 30 '13 at 4:39