blocks|key|3843913|text|这真的没什么大不了的。你可以只用一条命令做一个脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3843914|chmod+a%2Bx+*.pl|code-block|syntax|javascript|3843915|并在创建perl文件后运行该脚本。或者，您可以使用如下命令打开一个文件：|3843916|touch+filename.pl+&&+chmod+a%2Bx+filename.pl+&&+vi+filename.pl+#+choose+your+favorite+editor|3843917|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

It's really not that big of a deal. You could just make a script with the single command:

<pre><code>chmod a+x *.pl
</code></pre>

And run the script after creating a perl file. Alternatively, you could open a file with a command like this:

<pre><code>touch filename.pl &amp;&amp; chmod a+x filename.pl &amp;&amp; vi filename.pl # choose your favorite editor
</code></pre>

blocks|key|5261775|text|使文件成为可执行文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5261776|5261777|+chmod+%2Bx文件|blockquote|5261778|5261779|5261780|查找perl的位置：|5261781|5261782|哪一个perl|5261783|5261784|5261785|这应该返回类似如下的内容|5261786|5261787|+/bin/perl有时/usr/local/bin|5261788|5261789|5261790|然后在脚本的第一行添加：|5261791|5261792|+#!"+path+"/perl带有上面的路径，例如|5261793|5261794|#!/bin/perl|5261795|5261796|然后您就可以执行该文件了|5261797|文件./+|5261798|5261799|5261800|5261801|路径可能会有一些问题，所以您可能也想要更改它...|5261802|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1H|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1K|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|K|3|L|5|E|7|1M|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|1R|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1U|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|E|7|1W|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|20|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|21|8|@]|9|@]|A|$]]|$1|18|3|-4|5|E|7|22|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|25|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|1E|$]]

Make file executable:
<blockquote>
chmod +x file
</blockquote>
Find location of perl:
<blockquote>
which perl
</blockquote>
This should return something like
<blockquote>
/bin/perl sometimes /usr/local/bin
</blockquote>
Then in the first line of your script add:
<blockquote>
#!&quot;path&quot;/perl with path from above e.g.
#!/bin/perl
</blockquote>
Then you can execute the file
<blockquote>
./file
</blockquote>
There may be some issues with the PATH, so you may want to change that as well ...

blocks|key|3844013|text|你所描述的才是处理这个问题的正确方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3844014|你说过你想留在GUI里。通常可以通过文件属性菜单设置执行位。如果您愿意的话，您还可以学习如何为上下文菜单创建自定义操作来完成此操作。当然，这取决于您的桌面环境。|3844015|如果使用更高级的编辑器，则可以编写保存文件时发生的操作的脚本。例如(我只对vim很熟悉)，你可以把它添加到你的.vimrc中，使任何以"#!/*/bin/*“开头的新文件成为可执行文件。|offset|length|style|CODE|3844016|au+BufWritePost+*+if+getline(1)+=~+"%5E#!"+%7C+if+getline(1)+=~+"/bin/"+%7C+silent+!chmod+%2Bx+<afile>+%7C+endif+%7C+endif|code-block|syntax|javascript|3844017|entityMap^0|0|0|1W|A|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

What you describe is the correct way to handle this. 

You said that you want to stay in the GUI. You can usually set the execute bit through the file properties menu. You could also learn how to create a custom action for the context menu to do this for you if you're so inclined. This depends on your desktop environment of course.

If you use a more advanced editor, you can script the action to happen when the file is saved. For example (I'm only really familiar with vim), you could add this to your .vimrc to make any new file that starts with "<code>#!/*/bin/*</code>" executable.

<pre><code>au BufWritePost * if getline(1) =~ "^#!" | if getline(1) =~ "/bin/" | silent !chmod +x &lt;afile&gt; | endif | endif
</code></pre>

blocks|key|3844034|text|我认为您遇到的问题是，即使您可以在系统中设置自己的umask值，这也不允许您显式地控制gedit+(或您使用的任何编辑器)在新文件上设置的默认权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3844035|我相信这个细节已经被硬编码到gedit和大多数其他编辑器中了。改变它的选择是(a)修改你自己的gedit模块，或者(b)找到一个文本编辑器，它允许你为新文件设置默认权限。(对不起，我什么都不知道。)|3844036|鉴于此，不得不chmod你的文件真的不是那么糟糕，对吧？|3844037|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I think the problem you're running into is that, even though you can set your own umask values in the system, this does not allow you to explicitly control the default permissions set on a new file by gedit (or whatever editor you use).

I believe this detail is hard-coded into gedit and most other editors. Your options for changing it are (a) hacking up your own mod of gedit or (b) finding a text editor that allows you to set a preference for default permissions on new files. (Sorry, I know of none.)

In light of this, it's really not so bad to have to chmod your files, right?

blocks|key|1734707|text|不需要修改你的编辑器，或者切换编辑器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1734708|相反，我们可以想出一个脚本来监视您的开发目录和chmod文件的创建。这就是我在附加的bash脚本中所做的。您可能希望通读注释并根据需要编辑“config”部分，然后我建议将其放在$HOME/bin/目录中，并将其执行添加到$HOME/.login或类似文件中。或者您可以直接从终端运行它。|1734709|这个脚本确实需要inotifywait，它位于Ubuntu上的inotify-tools包中，|1734710|sudo+apt-get+install+inotify-tools|code-block|syntax|javascript|1734711|欢迎提出建议/编辑/改进。|1734712|#!/usr/bin/env+bash

#+---+usage+---+#
#+Depends:+'inotifywait'+available+in+inotify-tools+on+Ubuntu
#+
#+Edit+the+'config'+section+below+to+reflect+your+working+directory,+WORK_DIR,
#+and+your+watched+directories,+WATCH_DIR.+Each+directory+in+WATCH_DIR+will
#+be+logged+by+inotify+and+this+script+will+'chmod+%2Bx'+any+new+files+created
#+therein.+If+SUBDIRS+is+'TRUE'+this+script+will+watch+WATCH_DIRS+recursively.
#+I+recommend+adding+this+script+to+your+$HOME/.login+or+similar+to+have+it
#+run+whenever+you+log+into+a+shell,+eg+'echo+"watchdirs.sh+&"+>>+~/.login'.
#+This+script+will+only+allow+one+instance+of+itself+to+run+at+a+time.

#+---+config+---+#

WORK_DIR="$HOME/path/to/devel"+#+top+working+directory+(for+cleanliness?)
WATCH_DIRS="+\
++++$WORK_DIR/dirA+\
++++$WORK_DIR/dirC+\
++++"++++++++++++++++++++++++++#+list+of+directories+to+watch
SUBDIRS="TRUE"+++++++++++++++++#+watch+subdirectories+too
NOTIFY_ARGS="-e+create+-q"+++++#+watch+for+create+events,+non-verbose


#+---+script+starts+here+---+#
#+probably+don't+need+to+edit+beyond+this+point

#+kill+all+previous+instances+of+myself
SCRIPT="bash.*`basename+$0`"
MATCHES=`ps+ax+%7C+egrep+$SCRIPT+%7C+grep+-v+grep+%7C+awk+'{print+$1}'+%7C+grep+-v+$$`
kill+$MATCHES+>&+/dev/null

#+set+recursive+notifications+(for+subdirectories)
if+[+"$SUBDIRS"+=+"TRUE"+]+;+then
++++RECURSE="-r"
else
++++RECURSE=""
fi

while+true+;+do
++++#+grab+an+event
++++EVENT=`inotifywait+$RECURSE+$NOTIFY_ARGS+$WATCH_DIRS`

++++#+parse+the+event+into+DIR,+TAGS,+FILE
++++OLDIFS=$IFS+;+IFS="+"+;+set+--+$EVENT
++++E_DIR=$1
++++E_TAGS=$2
++++E_FILE=$3
++++IFS=$OLDIFS

++++#+skip+if+it's+not+a+file+event+or+already+executable+(unlikely)
++++if+[+!+-f+"$E_DIR$E_FILE"+]+%7C%7C+[+-x+"$E_DIR$E_FILE"+]+;+then
++++++++continue
++++fi

++++#+set+file+executable
++++chmod+%2Bx+$E_DIR$E_FILE
done|1734713|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

No need to hack your editor, or switch editors.

Instead we can come up with a script to watch your development directories and chmod files as they're created. This is what I've done in the attached bash script. You probably want to read through the comments and edit the 'config' section as fits your needs, then I would suggest putting it in your $HOME/bin/ directory and adding its execution to your $HOME/.login or similar file. Or you can just run it from the terminal.

This script does require inotifywait, which comes in the inotify-tools package on Ubuntu,

<pre><code>sudo apt-get install inotify-tools
</code></pre>

Suggestions/edits/improvements are welcome.

<pre><code>#!/usr/bin/env bash

# --- usage --- #
# Depends: 'inotifywait' available in inotify-tools on Ubuntu
# 
# Edit the 'config' section below to reflect your working directory, WORK_DIR,
# and your watched directories, WATCH_DIR. Each directory in WATCH_DIR will
# be logged by inotify and this script will 'chmod +x' any new files created
# therein. If SUBDIRS is 'TRUE' this script will watch WATCH_DIRS recursively.
# I recommend adding this script to your $HOME/.login or similar to have it
# run whenever you log into a shell, eg 'echo "watchdirs.sh &amp;" &gt;&gt; ~/.login'.
# This script will only allow one instance of itself to run at a time.

# --- config --- #

WORK_DIR="$HOME/path/to/devel" # top working directory (for cleanliness?)
WATCH_DIRS=" \
 $WORK_DIR/dirA \
 $WORK_DIR/dirC \
 " # list of directories to watch
SUBDIRS="TRUE" # watch subdirectories too
NOTIFY_ARGS="-e create -q" # watch for create events, non-verbose


# --- script starts here --- #
# probably don't need to edit beyond this point

# kill all previous instances of myself
SCRIPT="bash.*`basename $0`"
MATCHES=`ps ax | egrep $SCRIPT | grep -v grep | awk '{print $1}' | grep -v $$`
kill $MATCHES &gt;&amp; /dev/null

# set recursive notifications (for subdirectories)
if [ "$SUBDIRS" = "TRUE" ] ; then
 RECURSE="-r"
else
 RECURSE=""
fi

while true ; do
 # grab an event
 EVENT=`inotifywait $RECURSE $NOTIFY_ARGS $WATCH_DIRS`

 # parse the event into DIR, TAGS, FILE
 OLDIFS=$IFS ; IFS=" " ; set -- $EVENT
 E_DIR=$1
 E_TAGS=$2
 E_FILE=$3
 IFS=$OLDIFS

 # skip if it's not a file event or already executable (unlikely)
 if [ ! -f "$E_DIR$E_FILE" ] || [ -x "$E_DIR$E_FILE" ] ; then
 continue
 fi

 # set file executable
 chmod +x $E_DIR$E_FILE
done
</code></pre>

One thing I plan to be doing is writing (painfully simple) Perl scripts, and I'd like to be able to run them without explicitly calling Perl from the terminal. I appreciate that, to do this, I need to grant them execute permissions. Doing this with chmod is easy enough, but it also seems like a slightly laborious extra step. What I would like is one of two things:

Firstly, is there a way to set the execute flag when saving a file? Currently I'm experimenting with gedit and geany, but would be willing to switch to a similarly- (or better-) featured editor if it had this capability.

Failing that, is there a way to declare that all files created in a particular directory should have execute permissions?

My umask is set to 022, which should be OK, as far as I understand, but it would appear that the files are created as text files (with 666 default permissions) rather than executable files (with 777 default permissions).

Perhaps I'm just being lazy, but I figure there must be a more convenient way than chmodding every single script one creates.

Creating executable files in Linux

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我计划做的一件事是编写(极其简单的) Perl脚本，我希望能够在不从终端显式调用Perl的情况下运行它们。我意识到，要做到这一点，我需要授予他们执行权限。用chmod做这件事很容易，但这似乎也是一个稍微费力的额外步骤。我想要的是两件事中的一件：首先，有没有办法在保存文件时设置执行标志？目前我正在试验gedit和gean...

问在Linux中创建可执行文件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Linux中创建可执行文件EN