On 07.09.2007, at 20:34, source_changes@macosforge.org wrote:
+ # -*- Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4
Shouldn't there be a "coding: utf-8" in there, at least for Portfiles? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On Sep 9, 2007, at 15:48, Jochen Küpper wrote:
On 07.09.2007, at 20:34, source_changes@macosforge.org wrote:
+ # -*- Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4
Shouldn't there be a "coding: utf-8" in there, at least for Portfiles?
Portfiles must be utf-8, so whatever we can do to inform emacs and vim of that should be done.
On Sep 9, 2007, at 4:48 PM, Jochen Küpper wrote:
On 07.09.2007, at 20:34, source_changes@macosforge.org wrote:
+ # -*- Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4
Shouldn't there be a "coding: utf-8" in there, at least for Portfiles?
Greetings, Jochen
So, we need to come to a final agreement on the modelines we're going to impose/request in our source files/Portfiles: 1) Source files: # -*- coding: utf-8; Mode: Tcl; tab-width: 4; indent- tabs-mode: nil; c-basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4 2) Portfiles (it's the same as above, is that recommended?): # -*- coding: utf-8; Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4 3) Makefiles: # -*- Mode: Makefile; tab-width: 8; indent-tabs-mode: t -*- vim:noet:sw=8:ts=8 Any objections to those? Something to add? Is casing of keywords right (Tcl or tcl)? Once we agree on the exact formats we should document them and everyone should stick to them, even in the order of the components. Regards,... -jmpp PS: Actual conversion of the files will probably be implemented on a file by file basis, unfortunately, as a regex to convert everything in one fell swoop is very difficult to construct and very error prone, I believe (as also advised by Kevin).
On Sep 10, 2007, at 6:18 PM, Juan Manuel Palacios wrote:
On Sep 9, 2007, at 4:48 PM, Jochen Küpper wrote:
On 07.09.2007, at 20:34, source_changes@macosforge.org wrote:
+ # -*- Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4
Shouldn't there be a "coding: utf-8" in there, at least for Portfiles?
Greetings, Jochen
So, we need to come to a final agreement on the modelines we're going to impose/request in our source files/Portfiles:
1) Source files: # -*- coding: utf-8; Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4 2) Portfiles (it's the same as above, is that recommended?): # -*- coding: utf-8; Mode: Tcl; tab-width: 4; indent-tabs-mode: nil; c- basic-offset: 4 -*- vim:et:sw=4:ts=4:sts=4 3) Makefiles: # -*- Mode: Makefile; tab-width: 8; indent-tabs-mode: t -*- vim:noet:sw=8:ts=8
Any objections to those? Something to add? Is casing of keywords right (Tcl or tcl)?
I don't know if it makes a difference, not being an Emacs person, but I think the Mode keyword is supposed to come first. Also we should probably have file encoding in the modeline # -*- Mode: Tcl; coding: utf-8; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:et:sw=4:ts=4:sts=4
Once we agree on the exact formats we should document them and everyone should stick to them, even in the order of the components.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
Please forward to macports-dev@lists.macosforge.org, as I am not subscribed there (Cannot post) On 11.09.2007, at 00:51, Kevin Ballard wrote:
Any objections to those? Something to add? Is casing of keywords right (Tcl or tcl)?
Shouldn't matter; personally I lower-case these. The mode is actually called "tcl-mode" (not Tcl-mode) in Emacs. Therefore it should be lower-cased for clarity.
I don't know if it makes a difference, not being an Emacs person, but I think the Mode keyword is supposed to come first.
Actually: no. In principle it does also not matter, but many put the coding first, because that is the order in which that needs to be know. First you "decode" the file, then you switch to a mode, then you customize that... For vim you actually have the encoding first as well;)
Also we should probably have file encoding in the modeline
Right, also for vim. Thus we get this line: # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:et:sw=4:ts=4:sts=4 Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
Jochen Küpper wrote:
Please forward to macports-dev@lists.macosforge.org, as I am not subscribed there (Cannot post)
On 11.09.2007, at 00:51, Kevin Ballard wrote:
Any objections to those? Something to add? Is casing of keywords right (Tcl or tcl)?
Shouldn't matter; personally I lower-case these. The mode is actually called "tcl-mode" (not Tcl-mode) in Emacs. Therefore it should be lower-cased for clarity.
I don't know if it makes a difference, not being an Emacs person, but I think the Mode keyword is supposed to come first.
Actually: no. In principle it does also not matter, but many put the coding first, because that is the order in which that needs to be know. First you "decode" the file, then you switch to a mode, then you customize that... For vim you actually have the encoding first as well;)
Also we should probably have file encoding in the modeline
Right, also for vim.
Thus we get this line:
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:et:sw=4:ts=4:sts=4
Greetings, Jochen
Hi all I know it is a bit late, and I'm (still) an outsider, but shouldn't a filetype directive be included in the vim modeline? Especially for the Portfiles, as the filetype-plugin identifies them as configuration files. That would give something like: # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 Regards Michael
participants (5)
-
Jochen Küpper
-
Juan Manuel Palacios
-
Kevin Ballard
-
Michael Wild
-
Ryan Schmidt