blocks|key|1495994|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

I only have access to three current <code>ed</code> implementations:
<ol>
<li>OpenBSD 7.0 <code>ed</code> (expected to behave like <code>ed</code> on NetBSD, FreeBSD, and macOS, but I haven't tested this thoroughly).</li>
<li>GNU <code>ed</code> 1.14.2 and 1.16.</li>
<li>Plan 9 <code>ed</code> from <code>plan9port-20210323</code>.</li>
</ol>
I have tried to summarize the differences between these below, and I've also tried to add the expected behavior of some &quot;POSIX compliant <code>ed</code>&quot; (going by what <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ed.html" rel="nofollow noreferrer">the POSIX specification</a> says).
Only the differences that I have encountered in <code>ed</code>-related questions/answers here on U&amp;L are mentioned, so I haven't tried to make a literature study of manuals, etc., to find everything. For example, most <code>ed</code> implementations provide extensions to the POSIX <code>ed</code> standard through extra commands and/or command-line options should be fairly self-evident from their manuals, and the POSIX <code>ed</code> specification also mentions some commands that were never standardized.
The supported variants of regular expressions depend partly on the system's regular expression library. This means that the expression <code>\`</code> on a GNU system would match the start of a line (just like <code>^</code>) as shown in the GNU <code>ed</code> (info-)manual, whereas GNU <code>ed</code> on an OpenBSD system would not be able to use that. So I won't talk more about this.
These are some other differences:
<ul>
<li><code>#</code> as a comment character.
<ul>
<li>GNU: <code>#</code> is a comment command.</li>
<li>BSD: <code>#</code> is not a valid command.</li>
<li>Plan 9: Like BSD.</li>
<li>POSIX: Like BSD.</li>
</ul>
</li>
<li>Behavior destroying unsaved work.
<ul>
<li>GNU: <code>e</code>, <code>e !</code>, and <code>q</code> always fails on the first try if the buffer is unsaved.</li>
<li>BSD: Like GNU, but using <code>-s</code> disables the warning.</li>
<li>Plan 9: Like GNU.</li>
<li>POSIX: Like GNU.</li>
</ul>
</li>
<li>Exit status (this is a bit difficult to test thoroughly).
<ul>
<li>GNU: Terminates with a non-zero exit status if the last command caused
an error.</li>
<li>BSD: Most errors cause non-zero termination only with <code>-s</code>.</li>
<li>Plan 9: Seems to never terminate with non-zero exit status.</li>
<li>POSIX: Termination with a zero exit status means &quot;Successful completion
without any file or command errors.&quot;</li>
</ul>
</li>
<li>The <code>s///</code> command, but with only the first <code>/</code>.
<ul>
<li>GNU: <code>s/RE</code> is an error.</li>
<li>BSD: <code>s/RE</code> behaves like <code>s/RE/</code>, which is the same as <code>s/RE//p</code>, i.e.
it replaces the substring matching the regular expression <code>RE</code>
with nothing and prints the modified line.</li>
<li>Plan 9: Like BSD.</li>
<li>POSIX: Like GNU.</li>
</ul>
</li>
<li>Using <code>^</code> as an address.
<ul>
<li>GNU: <code>^</code> is an invalid address.</li>
<li>BSD: <code>^</code> addresses the previous line, just like <code>-</code>.</li>
<li>Plan 9: Like BSD.</li>
<li>POSIX: Permits <code>^</code> to be the same as <code>-</code>.</li>
</ul>
</li>
<li>Combining the printing commands <code>p</code>, <code>l</code>, and <code>n</code> (like <code>nl</code>), and repeating commands while doing so (as in <code>nlnl</code> or <code>pnnn</code>).
<ul>
<li>GNU: Combining printing commands is allowed. Repeated commands are not permitted (although <code>pp</code>, <code>nn</code>, and <code>ll</code> are allowed since the standard allows adding <code>p</code>, <code>n</code>, or <code>l</code> to commands other than <code>e</code>, <code>E</code>, <code>f</code>, <code>q</code>, <code>Q</code>, <code>r</code>, <code>w</code>, or <code>!</code>).</li>
<li>BSD: Combining printing commands is allowed. Repeated commands are permitted.</li>
<li>Plan 9: Combinations of two commands out of the three are permitted (not <code>nlp</code>). Repeated commands are not allowed.</li>
<li>POSIX: The effect of combining printing commands is &quot;unspecified&quot;.</li>
</ul>
</li>
<li>Upon receiving a HUP signal, the current editing buffer is saved in a file called <code>ed.hup</code> in the current directory. If that fails, the buffer is written to <code>$HOME/ed.hup</code>. What happens if these names already exist?
<ul>
<li>GNU: The file <code>ed.hup</code> in the current directory will be overwritten if it is a regular file and it's owned by the current user. Otherwise, the file <code>$HOME/ed.hup</code> will be overwritten if it is a regular file owned by the current user. Otherwise, the buffer is lost.</li>
<li>BSD: Like GNU, but the current buffer is also available in a temporary file whose name matches <code>/tmp/ed.*</code>.</li>
<li>Plan 9: Like GNU.</li>
<li>POSIX: Like GNU.</li>
</ul>
</li>
</ul>

I was wondering is there is any functional difference between Gnu Ed and the version of Ed which ships with BSD Unix systems? I am currently using Gnu Ed 1.17 on Debian 10 but discovered this page:
<a href="https://man.openbsd.org/ed" rel="nofollow noreferrer">https://man.openbsd.org/ed</a>
The man pages seem to differ:
<a href="https://www.gnu.org/software/ed/manual/ed_manual.html" rel="nofollow noreferrer">https://www.gnu.org/software/ed/manual/ed_manual.html</a>

What is the difference between Gnu Ed and the version of Ed that ships with Unix?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我想知道Gnu Ed和BSD Unix系统附带的Ed版本之间有什么功能上的区别吗？我目前正在Debian 10上使用Gnu Ed 1.17，但发现这个页面：https://man.openbsd.org/ed手册页似乎各不相同：https://www.gnu.org/software/ed/manual/ed_manual.html

问Gnu Ed和Unix附带的Ed版本有什么不同？
EN

回答 1

Unix & Linux用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gnu Ed和Unix附带的Ed版本有什么不同？EN