ini.syntax

[zaytsev]

​http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567046

From: Karsten Hilbert <karsten.hilbert@gmx.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: mc: INI syntax file proposition
Date: Tue, 26 Jan 2010 22:49:38 +0100
[Message part 1 (text/plain, inline)]
Package: mc
Version: 3:4.7.0.1-1
Severity: wishlist
Tags: patch
I am attaching a proposed syntax highlighting definition for
- gasp - DOS style INI files. You,
	[groups]
with
	option = value
and such. It would probably need to be tied to *.ini files.
Personally I also use it for *.conf files but that is by no
means safe to assume to be an INI style file.
I'd love to set the
	option
part in
	option = value
to some other color, too, but didn't find the proper syntax
for that.
Karsten

[zaytsev]

Branch: 2126_ini_syntax (parent: master)
Changeset: f25d1fbd2f53bcc618691be33022650b82ddce73

[zaytsev]

Could someone clever please tell me how to set option = value to some other color as per original request? I'd be happy to apply the patch and squash the branch.

[zaytsev]

Did anyone see my question above about highlighting of the first part? I have no clue how to implement this correctly, but if someone comes up with the solution after merge I'll have to reopen and merge again for just few lines... Egh?

[slavazanko]

See changeset:a25431452305fdc471bcccd3bdbcbe9b5965113f

Also, no need to create separate branch (and tickect) for syntax-highlight related patches: ​http://midnight-commander.org/wiki/WorkingGuideLines#Directcommits

[zaytsev]

Hi Slava!

Looks cool! Shall I merge this or you want to use this branch for something else? Sorry for creating the branch, I'm out of Jabber till at least next week. I would have asked there otherwise.

Z.

[slavazanko]

Shall I merge this or you want to use this branch for something else?

Just merge.

[zaytsev]

Committed to master. Merge changeset: bfd0b2c9953dfa5a0591ee243a1532ad44138463.
Cherry-picked to 4.7.0-stable, changeset: 03fdddfdccfa6eba501b66da208db032bdb44572.

[andrew_b]

Don't forget remove the merged branch.

[zaytsev]

Actually, I can't:

zyv@mypride:~/Documents/test/mc-git$ git push origin :2149_patchfs_single_line
error: unable to push to unqualified destination: 2149_patchfs_single_line
The destination refspec neither matches an existing ref on the remote nor
begins with refs/, and we are unable to guess a prefix based on the source ref.
error: failed to push some refs to 'ssh+git://midnight-commander.org/git/mc.git'

zyv@mypride:~/Documents/test/mc-git$ git push origin :refs/origin/2149_patchfs_single_line
warning: Allowing deletion of corrupt ref.
*** Unknown type of update to refs/origin/2149_patchfs_single_line ()
***  - no email generated
error: hooks/post-receive exited with error code 1
To ssh+git://midnight-commander.org/git/mc.git
 - [deleted]         refs/origin/2149_patchfs_single_line

zyv@mypride:~/Documents/test/mc-git$ git branch -r
  origin/2149_patchfs_single_line

I use the latest git FYI.

[slavazanko]

$ git pull
Already up-to-date.
$ git branch -r | grep -c 2149
0

Looks as your local problems. Check your loal copy of repo.

also, run:

git remote prune origin

for cleanup of removed branches.

[slavazanko]

and why you looking at '2149_patchfs_single_line' branch? Is this branch is actial for this ticket? :)

[zaytsev]

Thanks! The pruning thing fixed the issue for me. I couldn't delete this one, so I tried another one which I know was already merged.