If you mean when you open the file in the windows gVim it destroys the permissions, that is expected. Windows doesn't know about or understand the "Unix" permissions cygwin uses.
actually I thought about that.
Just as in unix/cygwin we place a
in the .profile/.bash_profile to overwrite the file creation mask, is there also a similar config file on windows that we can modify the file creation mask? I realized Windows (gVim) always sets the file permissions to a specific value, which means it has a default..
I have a linux Enterprise Server Version 3 (ES) . It does not have Gvim on it. Can someone tell me how I can get Gvim on it please. I have spent a fair bit of time researching this and have not figured it out. I am probably missing something simple.
Frank (1 Reply)
Hey folks,
I have used gVim in Windows for many years but I have never found an answer to a very simple question I am going to ask you guys...
My question is if there is a way to eliminate the creation of those ~ files that gVim creates in Windows. If you have ever used gVim in Windows you... (2 Replies)
I need to be very careful to keep ^M characters out of files.
In gVim, I can change the file format to Unix easily enough, but is there any way to make Unix the default format?
I can see "startup options" in the menu, but this takes me to some meaningless config file. I believe my config value... (1 Reply)
Hello All,
I am using gvim ( redhat linux machine). backspace doesnot work properly. can some boby suggest a solution ?
i have checked with older version. backspace works in it.
Thanks
Shiv (1 Reply)
Hi People,
Does gvim latest versions support tabs. I would like to open different files in tabs rather than new windows or split windows. I would like to whether the current version supports it, if it doesn't then how to add such feature.
Thanks,
:) (2 Replies)
I use sugarsync to sync my vimrc across computers. I keep the _vimrc file in a syncing folder and in my home folder, I have a symbolic link ~\_vimrc pointing to ~\Synced Docs\_vimrc. On my mac I have a .vimrc symbolic link pointing at the _vimrc file. On the pc side, every time I open the _vimrc... (3 Replies)
Hi, Dummy here!
I have a file in my directory named "jest". I wonder why I couldn't save change by using Shift + z + z which I used to do. But it work fine with :wq! command.
The second thing is, after several time of accessing the file, I notice my directory appears many files named jest~,... (1 Reply)
Hey all,
I work in a group environment where multiple people may end up editing the same file. We have measures in place so no two people can edit the same file at once. I have a script that does the following:
call: script file
The script will backup the file,
Moves the file to a... (2 Replies)
Discussion started by: Brusimm
2 Replies
LEARN ABOUT DEBIAN
umask
UMASK(2) Linux Programmer's Manual UMASK(2)NAME
umask - set file mode creation mask
SYNOPSIS
#include <sys/types.h>
#include <sys/stat.h>
mode_t umask(mode_t mask);
DESCRIPTION
umask() sets the calling process's file mode creation mask (umask) to mask & 0777 (i.e., only the file permission bits of mask are used),
and returns the previous value of the mask.
The umask is used by open(2), mkdir(2), and other system calls that create files to modify the permissions placed on newly created files or
directories. Specifically, permissions in the umask are turned off from the mode argument to open(2) and mkdir(2).
The constants that should be used to specify mask are described under stat(2).
The typical default value for the process umask is S_IWGRP | S_IWOTH (octal 022). In the usual case where the mode argument to open(2) is
specified as:
S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH
(octal 0666) when creating a new file, the permissions on the resulting file will be:
S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH
(because 0666 & ~022 = 0644; i.e., rw-r--r--).
RETURN VALUE
This system call always succeeds and the previous value of the mask is returned.
CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
NOTES
A child process created via fork(2) inherits its parent's umask. The umask is left unchanged by execve(2).
The umask setting also affects the permissions assigned to POSIX IPC objects (mq_open(3), sem_open(3), shm_open(3)), FIFOs (mkfifo(3)), and
UNIX domain sockets (unix(7)) created by the process. The umask does not affect the permissions assigned to System V IPC objects created
by the process (using msgget(2), semget(2), shmget(2)).
SEE ALSO chmod(2), mkdir(2), open(2), stat(2)COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-01-09 UMASK(2)