|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
create autogenerated files read-only
Sat Nov 12 09:22:47 2005, leo wrote:
Not the first time I or somenone else ran into the problem of editing an autogenerated file. Creating these files r/o would prevent from accidental changes. If someone could flesh out the intent of this ticket a bit more, I suspect someone fluent in Perl 5 could take it, since most files are written by Perl 5 processes. Some guidance as to how to create read-only files on various Ses would also be helpful. Thank you very much. kid51 |
|
#2
|
|||
|
|||
|
create autogenerated files read-only
Monday 17 March 2008 16:20:42 James Keenan via RT wrote:
If someone could flesh out the intent of this ticket a bit more, I suspect someone fluent in Perl 5 could take it, since most files are written by Perl 5 processes. > Some guidance as to how to create read-only files on various Ses would also be helpful. I had to add "set modeline" to my .vimrc, but now generated files respect the line: /* ex: set ro: when I edit them with Vim. Making sure that all generated files have a proper modeline seems like an easier solution than trying to get cross-platform file permissions working. -- c |
|
#3
|
|||
|
|||
|
create autogenerated files read-only
Monday 17 March 2008 16:20:42 James Keenan via RT wrote:
If someone could flesh out the intent of this ticket a bit more, I suspect someone fluent in Perl 5 could take it, since most files are written by Perl 5 processes. > Some guidance as to how to create read-only files on various Ses would also be helpful. I had to add "set modeline" to my .vimrc, but now generated files respect the line: /* ex: set ro: when I edit them with Vim. Making sure that all generated files have a proper modeline seems like an easier solution than trying to get cross-platform file permissions working. -- c |
|
#4
|
|||
|
|||
|
create autogenerated files read-only
Monday 17 March 2008 17:06:32 Bob Rogers wrote:
I had to add "set modeline" to my .vimrc, but now generated files respect the line: > /* ex: set ro: > when I edit them with Vim. > And adding "buffer-read-only: t" to "Local variables:" at the end will do the same for Emacs. These are the files in a pristine repository with 'ex: set ro:' in them; can you (or another Emacs user) edit them to add the appropriate tag for Emacs? config/gen/platform.pm config/gen/call_list.pm lib/Parrot//Utils.pm lib/Parrot/Manifest.pm lib/Parrot//Utils.pm MANIFEST MANIFEST.SKIP tools/build/jit2c.pl tools/build/pbcversion_h.pl tools/build/vtable_extend.pl tools/build/vtable_h.pl tools/build/c2str.pl tools/build/parrot_config_c.pl -- c |
|
#5
|
|||
|
|||
|
create autogenerated files read-only
Monday 17 March 2008 17:06:32 Bob Rogers wrote:
I had to add "set modeline" to my .vimrc, but now generated files respect the line: > /* ex: set ro: > when I edit them with Vim. > And adding "buffer-read-only: t" to "Local variables:" at the end will do the same for Emacs. These are the files in a pristine repository with 'ex: set ro:' in them; can you (or another Emacs user) edit them to add the appropriate tag for Emacs? config/gen/platform.pm config/gen/call_list.pm lib/Parrot//Utils.pm lib/Parrot/Manifest.pm lib/Parrot//Utils.pm MANIFEST MANIFEST.SKIP tools/build/jit2c.pl tools/build/pbcversion_h.pl tools/build/vtable_extend.pl tools/build/vtable_h.pl tools/build/c2str.pl tools/build/parrot_config_c.pl -- c |
|
#6
|
|||
|
|||
|
create autogenerated files read-only
Monday 17 March 2008 17:06:32 Bob Rogers wrote:
I had to add "set modeline" to my .vimrc, but now generated files respect the line: > /* ex: set ro: > when I edit them with Vim. > And adding "buffer-read-only: t" to "Local variables:" at the end will do the same for Emacs. These are the files in a pristine repository with 'ex: set ro:' in them; can you (or another Emacs user) edit them to add the appropriate tag for Emacs? config/gen/platform.pm config/gen/call_list.pm lib/Parrot//Utils.pm lib/Parrot/Manifest.pm lib/Parrot//Utils.pm MANIFEST MANIFEST.SKIP tools/build/jit2c.pl tools/build/pbcversion_h.pl tools/build/vtable_extend.pl tools/build/vtable_h.pl tools/build/c2str.pl tools/build/parrot_config_c.pl -- c |
|
#7
|
|||
|
|||
|
create autogenerated files read-only
9 days and no complaints; done.
-- Bob 2008-07-12 17:28:24: revision: 29361; author: rgrjr [CRE] Make Emacs coda read-only in generated files (part of #37664). =/trunk/MANIFEST: action: M =/trunk/MANIFEST.generated: action: M =/trunk/config/gen/call_list.pm: action: M =/trunk/config/gen/platform.pm: action: M =/trunk/lib/Parrot/Manifest.pm: action: M =/trunk/lib/Parrot//Utils.pm: action: M =/trunk/lib/Parrot//Utils.pm: action: M =/trunk/tools/build/c2str.pl: action: M =/trunk/tools/build/jit2c.pl: action: M =/ action: M =/ action: M =/ action: M =/trunk/tools/build/vtable_h.pl: action: M |
![]() |
| Viewing: Web Development Archives > Mailing Lists > Perl > create autogenerated files read-only |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|