ed2xwshq8l
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    <p>你不是缺少“一个 EA”,你缺的是一套能持续验证、能在不同市场状态下自我约束的交易流程。很多人做 ea量化交易 时最先踩的坑,是把回测曲线当成真实收益,把“能跑起来”当成“能活下来”,最后在一次点差扩大、滑点飙升或行情切换时,把前期利润一口气吐回去。</p> <p>作为长期跟踪外汇与多品种量化落地的团队,我们在 waihuifx 看到的高频失败模式非常一致:策略不区分行情环境、风险预算不清晰、执行与监控缺位。你真正需要的是把信号、执行、仓位和风控拆开设计,再用可复现的标准去筛选策略,而不是追逐“圣杯参数”。如果你正在寻找可落地的资料与工具入口,也可以从<a href="https://www.waihuifx.com/">ea量化交易</a>相关资源开始建立你的工作台。</p> <p>ea量化交易是指使用预先写好的规则与程序(EA/算法)自动完成入场、加减仓、止损止盈与退出。它把交易决策从情绪中剥离出来,通过可回测、可监控的方式执行策略。它并不等于稳赚,而是把“可验证”变成第一原则。</p> <h2>Key Takeaways</h2> <ul> <li>先定义市场状态与策略适配边界,再决定是否让 EA 上线实盘。</li> <li>用同一套风控预算评估不同策略,避免用收益掩盖尾部风险。</li> <li>回测必须包含点差、滑点与交易成本敏感性测试,否则结果偏乐观。</li> <li>把监控指标前置到上线前,设定可执行的熔断与降频触发条件。</li> <li>用走样检测与再训练节奏处理失效,不要靠频繁改参数自我安慰。</li> </ul> <p>Quick Answer:ea量化交易是用自动化程序按规则交易,并用回测与实时监控验证这些规则在不同市场环境中的稳定性。它的优势是执行一致、可规模化;关键难点是成本、滑点与行情切换导致的失效。做得好的核心是“先风控后收益”,把可复现的验证流程放在第一位。</p> <h2>Table of Contents</h2> <ul> <li><a href="what-ea-quant-trading-really-is">什么是 ea量化交易: 你需要的不是概念而是边界</a></li> <li><a href="why-ea-fails-in-live-markets">为什么很多 EA 实盘会失效: 成本与市场状态</a></li> <li><a href="strategy-types-and-where-they-fit">常见策略类型与适用场景: 趋势、均值回归与突破</a></li> <li><a href="backtesting-that-doesnt-lie">不撒谎的回测: 数据、成本与稳健性检验</a></li> <li><a href="risk-management-playbook">风险管理作战手册: 仓位、熔断与相关性</a></li> <li><a href="execution-and-monitoring">执行与监控: 让 EA 像系统而不是脚本</a></li> <li><a href="case-studies-from-waihuifx">waihuifx 实战案例: 从回测到上线的取舍</a></li> <li><a href="common-misjudgments-and-failure-signals">常见误判与失败信号: 何时不该继续跑</a></li> <li><a href="future-trends-2026">2026 走向: 合规、AI 与多资产联动</a></li> <li><a href="conclusion">Conclusion</a></li> <li><a href="references">References</a></li> <li><a href="faq">FAQ</a></li> </ul> <p>Methodology:本文观点来自我们对真实交易日志的复盘、对同策略在不同点差与滑点假设下的回测对照、以及上线后以回撤阈值和成交质量为核心的监控指标。数据引用以公开机构报告为主,结论以“可复现的验证步骤”表达,便于你自行复核。</p> <h2 id="what-ea-quant-trading-really-is">什么是 ea量化交易: 你需要的不是概念而是边界</h2> <p>把 ea量化交易 讲清楚,最重要的不是“它能自动下单”,而是它必须有明确边界:在哪些品种、哪些时段、哪些波动水平、哪些点差区间内有效。一套策略如果不能回答这些问题,本质上只是“在历史里恰好拟合过”。</p> <p>在编辑与评估策略时,我习惯把 EA 拆成四层:信号层(为什么进场)、执行层(如何成交)、仓位层(下多大)、风控层(何时停)。多数新手只盯着信号层,忽略执行与风险,导致“回测很好、实盘很惨”。</p> <h3>ea量化交易适合新手吗?</h3> <p>适合,但前提是你把它当成“纪律系统”而不是“躺赚机器”。新手更容易受情绪影响,EA 的一致执行能减少冲动交易;但新手也更容易忽视成本、滑点与极端行情。建议从低杠杆、低频策略开始,先建立监控与熔断,再谈扩大资金与频率。</p> <div> <p>Pro Tip:先用“可停止的策略”上手。任何 EA 上线前,你都应该写出三条明确停机条件,例如连续亏损次数、最大日回撤、点差异常阈值。</p> </div> <h2 id="why-ea-fails-in-live-markets">为什么很多 EA 实盘会失效: 成本与市场状态</h2> <p>实盘与回测最大的差别是交易摩擦:点差浮动、滑点、延迟、拒单、隔夜利息与流动性断层。2024 年 BIS(国际清算银行)关于外汇市场结构的相关研究与统计反复强调:流动性在不同交易时段与事件窗口高度不均匀,成交质量并不稳定。EA 若没有把“成交质量”纳入模型,失效几乎是必然。</p> <p>第二个原因是市场状态切换。均值回归策略在窄幅震荡里很舒服,但在趋势加速期会持续逆势;突破策略在单边行情里收割,但在假突破密集的环境里会被来回打脸。你需要的不是“万能 EA”,而是“能识别自己不该工作”的 EA。</p> <h3>为什么回测盈利的 EA 一到实盘就亏?</h3> <p>常见原因是回测低估了交易成本与执行偏差:历史点差被固定、滑点被忽略、成交按理想价计算。实盘里点差会在新闻、开盘、流动性变薄时扩大,滑点会吞掉本来就不厚的边际优势。若策略每笔只赚几到十几点,成本稍微上升就足以把正期望翻成负期望。</p> <blockquote> <p>“我以前只看净利润曲线,后来才明白,真正决定能不能活下去的是回撤结构和成交质量。曲线漂亮不代表你能扛过一次行情状态变化。”</p> </blockquote> <h2 id="strategy-types-and-where-they-fit">常见策略类型与适用场景: 趋势、均值回归与突破</h2> <p>策略类型不是标签,而是“风险形状”。你选什么类型,决定你会在哪些时刻最痛。把策略与市场环境对齐,能显著减少无意义的亏损。</p> <ul> <li>趋势跟随:容忍小亏多次,抓住少数大波段;怕震荡、怕假突破。</li> <li>均值回归:在区间里稳定吃小利润;怕趋势延展、怕波动突变。</li> <li>区间突破:吃波动扩张;怕震荡区的反复假信号。</li> <li>套利/价差类:依赖报价质量与执行;怕相关性破裂与流动性骤降。</li> </ul> <table> <tr> <th>策略类型</th> <th>Best For</th> <th>Risk Level</th> <th>Typical Mistake</th> </tr> <tr> <td>趋势跟随(如均线+波动过滤)</td> <td>单边行情、波动稳步抬升的阶段</td> <td>中</td> <td>在震荡期不降频,导致小亏叠加成大回撤</td> </tr> <tr> <td>均值回归(如布林带回归)</td> <td>区间震荡、点差稳定的交易时段</td> <td>中到高</td> <td>逆势加仓或网格扩张,遇到趋势会“越补越亏”</td> </tr> <tr> <td>突破(如箱体突破+成交过滤)</td> <td>重大事件后、波动扩张与趋势形成期</td> <td>中</td> <td>不做假突破过滤,频繁止损打滑点</td> </tr> <tr> <td>新闻事件规避型(过滤交易窗口)</td> <td>以稳定执行为优先、降低极端滑点</td> <td>低到中</td> <td>过滤过度导致样本太少,统计显著性不足</td> </tr> <tr> <td>多品种分散组合(相关性控制)</td> <td>资金较大、追求回撤更平滑的账户</td> <td>中</td> <td>误把“多品种”当分散,忽略同向风险暴露</td> </tr> </table> <h2 id="backtesting-that-doesnt-lie">不撒谎的回测: 数据、成本与稳健性检验</h2> <p>回测不是为了证明你对,而是为了尽早证明你错。2023-2025 年多家机构研究都在强调同一个结论:策略回测最常见的偏差来自数据质量与过拟合。以 2024 年 JPMorgan 的市场观察与策略研究观点为例(公开研究中多次提及):在交易成本上升或流动性下降的阶段,很多“微利高频模型”的胜率并不足以抵消摩擦。</p> <p>我做回测时会强制加入三类检验:成本敏感性、参数稳健性、样本外验证。只要其中一项不过关,就把策略降级为“研究中”,而不是急着上线。</p> <ol> <li>Scan 数据来源与时间覆盖,确认包含高波动事件与不同交易时段。</li> <li>Mark 关键成本假设,加入浮动点差与滑点区间(例如 0.2-1.5 倍常态)。</li> <li>Confirm 样本外划分,至少做一次滚动窗口验证而不是单次切分。</li> <li>Manage 参数扰动测试,让关键参数在合理范围内抖动并观察回撤是否爆炸。</li> <li>Review 交易分布,检查盈利是否依赖少数“运气单”,并评估尾部亏损。</li> </ol> <div> <p>Pro Tip:别只看“最大回撤”一个数字。要看回撤发生的速度、持续时间、以及回撤后恢复所需的交易次数。这三项决定了你是否会在最糟糕的时刻手动干预。</p> </div> <h3>回测里最容易被忽视的指标是什么?</h3> <p>成交相关指标最容易被忽视:每笔平均盈利与平均成本的比值、在不同点差区间下的期望变化、以及交易集中发生在什么时段。如果你的优势只比成本高一点点,那么任何执行偏差都会把优势抹平。把“每笔期望/成本比”作为硬阈值,会比盯胜率更有效。</p> <h2 id="risk-management-playbook">风险管理作战手册: 仓位、熔断与相关性</h2> <p>做 ea量化交易 最现实的一句话是:你无法避免亏损,但你可以设计亏损的形状。专业风控不是“少亏点”,而是让你在坏运气叠加时仍然能继续交易。</p> <p>我建议用“三层风控”:</p> <ul> <li>单笔层:固定风险或波动调整风险(例如按 ATR 设止损与仓位)。</li> <li>日内层:最大日亏损、最大连续亏损次数、异常点差熔断。</li> <li>组合层:品种相关性与方向暴露上限,避免同一宏观因素导致一起爆仓。</li> </ul> <p>两条常被忽略、但极实用的规则:</p> <ul> <li>如果策略依赖高胜率,必须限制“单次亏损放大”,否则一次黑天鹅会抹掉数月利润。</li> <li>如果策略依赖少数大盈利,必须接受长时间横盘与小亏,否则你会在趋势到来前放弃。</li> </ul> <h2 id="execution-and-monitoring">执行与监控: 让 EA 像系统而不是脚本</h2> <p>把 EA 当成系统,就要像运营系统一样做监控与告警。你要监控的不仅是净值,还有“它是否按预期执行”。当我在 waihuifx 带团队做策略上线评审时,最常问的不是“能赚多少”,而是“当它偏离预期时,你准备怎么处理”。</p> <p>一套可落地的监控面板,至少要包含:</p> <ul> <li>成交质量:平均滑点、拒单率、成交延迟、点差分布。</li> <li>策略健康:近 N 笔期望变化、回撤斜率、交易频率漂移。</li> <li>风险暴露:同向敞口、事件窗口持仓、隔夜风险占比。</li> </ul> <p>如果你需要把“指标-阈值-动作”做成模板化流程,很多交易者会从<a href="https://www.waihuifx.com/">ea量化交易</a>的实操资料里找灵感,然后按自己的品种与时区改成可执行的检查表。</p> <h2 id="case-studies-from-waihuifx">waihuifx 实战案例: 从回测到上线的取舍</h2> <p>我讲两个我亲历的案例,都是“回测看起来不错”,但最终能否上线取决于你是否愿意面对真实世界的摩擦。</p> <p>案例一:趋势策略在“漂亮回测”里被成本打回原形。我们在一套 EURUSD 的趋势策略上,回测显示年化收益可观、最大回撤可控。但我要求团队做成本敏感性:把点差从常态上调 0.3-0.6 个点、加入更保守的滑点假设,结果期望收益几乎被吃光。最后我们做了两个取舍:一是降低交易频率,二是加入波动过滤与时段过滤,只在流动性更稳定的窗口交易。调整后曲线没那么“好看”,但实盘更接近回测。</p> <p>案例二:均值回归策略差点因为“抗亏损能力”不够而被否决。另一套策略在震荡环境里连续小赚,但在趋势拉升时会出现连续止损。我们在上线前把“连续亏损熔断”写进系统:连续亏损达到阈值自动降频,并在宏观事件窗口直接暂停。上线后有一次行情状态切换,熔断触发把回撤控制在预算内。那次之后我更确信:风控不是附加功能,是策略的一部分。</p> <blockquote> <p>“真正的稳定来自你愿意承认策略会失效,并提前写好它失效时的处理脚本。”</p> </blockquote> <h2 id="common-misjudgments-and-failure-signals">常见误判与失败信号: 何时不该继续跑</h2> <p>你需要一些“停止信号”,而不是无限优化。下面这些是我反复见到的误判与失败征兆,符合任意两条,就该立刻降频或停机复盘。</p> <ul> <li>常见误判:把高胜率当安全感。失败信号是盈亏比持续下降、偶发亏损变成“灾难单”。</li> <li>常见误判:频繁改参数等于优化。失败信号是参数越改越敏感,稍微变动就爆回撤。</li> <li>失败信号:交易次数突然飙升或骤降,说明信号条件在新环境下被误触发或失效。</li> <li>失败信号:滑点与点差分布明显右移,而策略每笔优势没有同步提高。</li> </ul> <h3>怎样判断 EA 是否进入“过拟合后遗症”阶段?</h3> <p>最直观的表现是:样本外表现显著差于样本内,而且你每次“微调”都只能短暂改善,随后更快恶化。另一个信号是参数稳定区间变窄,轻微扰动就让收益从正变负。遇到这种情况,优先回到策略逻辑与市场机制层面重构,而不是继续在参数上打补丁。</p> <h2 id="future-trends-2026">2026 走向: 合规、AI 与多资产联动</h2> <p>2026 的关键词不是“更神的指标”,而是更严格的可验证性、更透明的风险披露、以及更现实的执行建模。根据 2024 年 Gartner 对 AI 与自动化在金融应用中的研究观点(报告与公开解读中常见结论):能落地的自动化系统往往把监控、审计与风险约束放在与模型同等重要的位置。对量化交易者来说,这意味着你需要把日志、版本管理与异常处理做成标配。</p> <p>另一个趋势是多资产联动:外汇、指数、贵金属与数字资产之间的风险传导更快。单一品种的“局部最优”更容易被宏观冲击打破,因此组合层的相关性控制会越来越像刚需。</p> <h2 id="conclusion">Conclusion</h2> <p>ea量化交易的价值在于把交易变成可复现的工程:规则清晰、验证严格、执行一致、风险可控。它不会替你消灭风险,但能让你把风险写进系统,让错误更早暴露、让账户更耐用。如果你打算把它当成长期技能,而不是一次性赌运气,你会更接近稳定。</p> <p>waihuifx 推荐的下一步行动:</p> <ul> <li>建立“上线清单”:把成本敏感性、样本外验证、熔断条件写成文档,并逐条打勾通过。</li> <li>设置硬阈值:例如最大日回撤、连续亏损次数、点差异常范围;触发即自动停机复盘。</li> <li>先小资金跑 20-40 个交易日:只评估成交质量与回撤结构,达标后再考虑扩仓与加品种;需要资料可参考<a href="https://www.waihuifx.com/">ea量化交易</a>相关内容做模板化落地。</li> </ul> <h2 id="references">References</h2> <ul> <li>Bank for International Settlements(BIS),外汇市场结构与流动性相关研究(用于说明流动性分层与成交质量不稳定对策略的影响)。</li> <li>Gartner(2024),关于 AI 与自动化系统在金融场景落地的研究与公开解读(用于强调监控、审计与风险约束的重要性)。</li> <li>JPMorgan(2024-2025),市场观察与策略研究的公开内容与观点汇总(用于说明交易成本与流动性变化对微利策略的侵蚀)。</li> </ul> <h2 id="faq">FAQ</h2> <h3>ea量化交易需要会编程吗?</h3> <p>不一定,但你必须会“验证”。你可以使用现成 EA 或可视化工具搭建策略,但至少要懂回测设置、成本假设、样本外验证与监控阈值。不会编程的风险在于无法审计逻辑细节,因此更要用严格的测试与小资金试运行来弥补。</p> <h3>EA 上线实盘前最少要做哪些测试?</h3> <p>至少三类:样本外验证(避免只在历史一段时间有效)、成本敏感性(点差与滑点上调后是否仍为正期望)、参数稳健性(关键参数扰动后回撤是否可控)。如果你的策略在更保守的成本假设下立刻转负,先别上线。</p> <h3>如何设置止损才不会被频繁扫掉?</h3> <p>先问策略属于哪种风险形状。趋势策略通常需要更宽的止损并配合降频,均值回归需要严格限制逆势扩张。更通用的方法是用波动指标(如 ATR)做动态止损,再用“单笔风险占比”控制仓位,而不是用固定点数套所有市场状态。</p> <h3>网格和马丁类 EA 还能做吗?</h3> <p>可以研究,但要把它当成“尾部风险换平滑曲线”的结构性交易。你必须设置明确的最大层数、最大风险预算与强制退出机制,并在回测中加入极端趋势与点差扩大的情景测试。若你无法接受偶发的大回撤或长时间修复期,就不应使用这类结构。</p> <h3>我应该用多少资金开始跑量化?</h3> <p>用你愿意为“学习成本”付出的资金开始,并且把目标设为验证系统而不是赚钱。实操上,先用小资金覆盖至少 20-40 个交易日,观察回撤斜率、成交质量与信号频率漂移。只有当这些指标稳定达标,再逐步加仓,而不是一次性放大。</p> <h3>EA 需要每天盯盘吗?</h3> <p>不需要盯盘,但需要盯“指标”。你应该每天或每周查看成交质量、回撤结构、异常点差、交易频率与策略期望变化。自动化不是放任不管,而是把关注点从价格涨跌转移到系统是否偏离预期。</p>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully