is6gwlltb0
    • 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>你可能已经见过这种场景:方向对了,但一次“下单太大”就把一个月利润打回原形;或者更常见,连续几笔小亏看似无伤大雅,等你回头复盘才发现,是仓位失控让回撤变成了趋势。解决它不靠意志力,靠可重复的计算与纪律,而这正是頭寸大小計算器要做的事。</p> <p>如果你在意长期存活率,而不只是某一笔“押对”的刺激感,那么把头寸量化成公式几乎是必修课。zfx-online 在交易执行与风险框架上强调同一件事:先定义最大可承受损失,再让仓位自动服从,而不是让情绪决定手数。</p> <p>頭寸大小計算器是一种把“账户风险额度、止损距离与品种价值”连接起来的工具,用来计算每一笔交易应买卖多少数量。它的目标不是让你赚得更快,而是让你在坏运气与错误判断出现时,仍能按计划继续交易。</p> <h2>Key Takeaways</h2> <ul> <li>先固定每笔风险占比,再用止损距离反推仓位,避免手数随情绪波动。</li> <li>把点值、合约乘数与汇率转换写入计算,跨品种才不会“看错风险”。</li> <li>遇到波动放大时缩小头寸,而不是加码硬扛,让回撤保持可恢复。</li> <li>用交易日志核对实际滑点与成交价,定期校准计算器参数而非凭感觉。</li> <li>当止损无法合理设置时宁可不做,仓位计算不能替代策略有效性。</li> <li>把最大日亏与最大周亏设为第二道闸门,防止连续亏损引发报复交易。</li> </ul> <p>Quick Answer:頭寸大小計算器通过“账户规模 × 单笔风险比例 ÷(止损距离 × 每点价值)”计算可交易数量。它让每一笔交易的最坏情况损失可预测、可控制。只要止损位置改变,仓位就必须随之改变。</p> <h2>Table of Contents</h2> <ul> <li><a href="why-position-sizing-matters">为什么仓位决定你的生存率</a></li> <li><a href="inputs-you-must-get-right">必须算对的关键输入项</a></li> <li><a href="core-formulas-and-examples">核心公式与可落地的算例</a></li> <li><a href="workflow-for-real-trading">把计算器嵌入真实交易流程</a></li> <li><a href="case-study-from-the-desk">实战案例:我如何用仓位规则止住回撤</a></li> <li><a href="common-mistakes-and-failure-signals">常见误判与失败信号</a></li> <li><a href="tools-checklists-and-comparison">工具清单与场景对比表</a></li> <li><a href="advanced-risk-controls-2026">2026 的进阶风险控制:波动率、相关性与组合层面</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:本文的计算口径以“固定风险金额 + 明确止损距离”为基准,并用不同品种的点值/合约乘数做交叉校验。关键结论来自我们对交易日志(含滑点与跳空)、常见经纪商合约规格说明,以及公开机构在 2023-2026 年间对风险与波动的研究数据的对照整理。示例参数采用可复现实盘区间,便于你用自己的账户替换验证。</p> <h2 id="why-position-sizing-matters">为什么仓位决定你的生存率</h2> <p>策略会失误,市场会反常,但仓位失控通常是“不可逆”的:它会把一次普通亏损放大成需要更高收益率才能回本的深坑。举个简单数学:当账户回撤 20%,需要 25% 才回到原点;回撤 50%,需要 100% 才能回本。仓位越大,越容易把小概率事件变成大概率破产。</p> <p>仓位管理还有一个常被忽略的作用:它让你能持续执行同一套边际优势。策略的胜率与盈亏比只有在样本量足够大时才稳定显现,而超额仓位会让你在样本量还没累积起来之前就“被迫出局”。</p> <p>根据国际清算银行(BIS)对市场波动与流动性变化的研究综述(2023-2024 年间多次更新),在流动性收缩与波动扩张阶段,价格跳跃与滑点风险显著上升。仓位规则的价值就在于:当你的执行质量变差时,你的风险仍可被上限约束。</p> <h3>仓位管理和止损有什么区别?</h3> <p>止损决定“你何时认错”,仓位决定“认错要付多少钱”。同样是 50 点止损,1 手和 0.2 手带来的资金曲线压力完全不同。止损是空间问题,仓位是金额问题;两者必须配套,否则止损再精确也可能因仓位过大而变成账户级灾难。</p> <div> <p>Pro Tip:如果你经常“止损放很近但仍然亏很多”,优先检查点值与合约乘数是否算错,其次检查是否把“最大可承受亏损”误设成“我希望的亏损”。</p> </div> <h2 id="inputs-you-must-get-right">必须算对的关键输入项</h2> <p>頭寸大小計算器看起来只需要几个数字,但真正决定准确性的,是你是否把“品种的计价方式”理解清楚。尤其在外汇、指数、黄金、加密与期货之间切换时,点值、合约单位、最小变动价位与保证金口径很容易混在一起。</p> <ul> <li>账户净值:用实时权益(Equity)而非余额(Balance),否则浮亏/浮盈会让风险失真。</li> <li>单笔风险比例:常见是 0.25% 到 2%,新手更适合从 0.5% 起步。</li> <li>止损距离:必须来自结构位或波动率逻辑,而不是“看起来差不多”。</li> <li>每点价值:外汇取决于货币对与账户计价币种;指数/期货取决于合约乘数。</li> <li>预期滑点与跳空缓冲:在新闻、开盘、低流动性时段,建议增加缓冲。</li> </ul> <p>如果你想把这些输入快速落地,很多交易者会用 <a href="https://www.zfx-online.com/">頭寸大小計算器</a> 把止损距离与风险金额自动联动,避免在不同品种之间手工换算时出错。</p> <h3>单笔风险百分比设多少才合理?</h3> <p>没有统一标准,但可以用“最大可承受连亏”反推。比如你希望在连续 10 笔亏损后回撤不超过 10%,单笔风险就不应高于约 1%。如果你的策略胜率波动很大或交易频率很高,建议更低,给滑点、跳空与情绪错误留出冗余。</p> <h2 id="core-formulas-and-examples">核心公式与可落地的算例</h2> <p>最通用的计算框架可以写成一句话:先把“最多愿意亏多少钱”算出来,再用止损距离把这笔钱分摊到每一点的价值上,得到可交易数量。</p> <p>公式一(固定风险金额):风险金额 = 账户净值 × 单笔风险比例。</p> <p>公式二(仓位大小):仓位数量 = 风险金额 ÷(止损距离 × 每点价值)。</p> <p>你需要注意:每点价值不是固定常数。外汇中它会随货币对、手数单位与账户币种变化;指数与期货则通常由合约乘数定义。加密合约还可能涉及面值与标记价格机制。</p> <ol> <li>Scan:扫描品种合约规格,确认最小波动与合约乘数或点值规则。</li> <li>Mark:标注结构止损位置,写出从入场到止损的真实距离(含缓冲)。</li> <li>Confirm:确认账户权益与单笔风险比例,并设定最大日亏上限。</li> <li>Manage:用公式计算仓位并下单,确保止损与仓位同时生效。</li> <li>Review:复盘成交价与滑点,把偏差记录到参数里用于下次校准。</li> </ol> <blockquote> <p>“我不再问自己这笔能赚多少,而是先问:如果错了,我愿意付多少钱。这个问题让我的交易突然变得可执行。”</p> </blockquote> <h2 id="workflow-for-real-trading">把计算器嵌入真实交易流程</h2> <p>很多人会算,但仍然会在关键时刻“手动改大”。原因通常不是不懂公式,而是流程里没有强制约束。我的建议是把仓位计算放在入场按钮之前,像安全带一样:不扣上就不开车。</p> <p>一个可复制的工作流是:先定风险金额,再找止损位置,最后才谈入场与加仓。反过来做的人往往会为了“想要的手数”去挪止损,风险在不知不觉中被放大。</p> <p>当你在多个品种间切换时,最容易出错的是点值换算与止损距离单位。把计算动作固定在同一个工具里,并在下单前做一次“最坏情况金额”口头复述,会显著减少低级错误。中高频交易者尤其需要这种机械化步骤。</p> <div> <p>Pro Tip:把“最大可承受损失金额”写进下单备注里,例如“本笔最大亏损 120 美元”。如果你发现自己在下单时不好意思写出来,通常意味着仓位过大。</p> </div> <h3>什么时候应该重新计算仓位?</h3> <p>只要止损位置变化、波动显著变化或账户权益变化,就应该重新计算。最典型的是你移动止损到更远的位置却不愿减少仓位,这会让实际风险倍增。另一个触发条件是交易时段切换:从常态流动性进入数据公布或开盘阶段时,滑点预期应上调,仓位应下调。</p> <h2 id="case-study-from-the-desk">实战案例:我如何用仓位规则止住回撤</h2> <p>我曾经在一段波动扩张的行情里吃过亏:连续两周我判断趋势方向大体没错,但账户还是不断回撤。复盘时发现,真正的“错误”不是方向,而是每次遇到假突破就被扫损,止损距离扩大后我却维持了原手数,单笔风险从 1% 悄悄爬到接近 2.5%。</p> <p>我把流程改成硬约束:任何一笔交易,只允许先输入“账户权益、单笔风险、止损距离”,再由工具给出手数上限。我用 zfx-online 的 <a href="https://www.zfx-online.com/">頭寸大小計算器</a> 做这个动作,结果很直观:同一品种在那段时间里,仓位普遍需要缩小 30% 到 55%。接下来的 18 笔交易里,我依然有连亏,但最大回撤被锁在我设定的阈值以内,策略才有机会把优势兑现出来。</p> <p>另一次更典型:一位做指数短线的朋友来找我看交易记录。他的胜率不低,但遇到连续两笔亏损就加倍“追回来”,第三笔往往爆掉。我让他做两件事:第一,把日内最大亏损设为账户的 2%;第二,每一笔交易都用同一口径计算仓位,且止损必须先落地。两周后他给我看曲线:盈利没有暴涨,但回撤明显变浅,交易次数也更稳定。</p> <blockquote> <p>“最难的不是算出手数,而是承认自己必须用更小的手数活下去。仓位变小后,我反而更敢按计划执行。”</p> </blockquote> <h2 id="common-mistakes-and-failure-signals">常见误判与失败信号</h2> <p>仓位计算不是万能钥匙。它能控制单笔风险,却不能替你保证策略有效、流动性充足或执行稳定。下面这些误判很常见,尤其会在你感觉“自己最近状态不错”时出现。</p> <ul> <li>误判:用保证金占用来判断风险。纠错:保证金是门槛,不是最坏损失;风险以止损触发的亏损金额衡量。</li> <li>误判:止损越小越安全。纠错:止损过小会让噪音扫损增多,导致你用更大手数“补偿”,反而放大回撤。</li> <li>误判:同样的点数波动在不同品种风险相同。纠错:点值/合约乘数不同,同样 50 点可能是完全不同的美元风险。</li> </ul> <p>失败信号也需要明确定义,否则你会把“偶尔出错”变成“系统性失控”。这里给两条可自检的红线。</p> <ul> <li>失败信号:你开始移动止损只为保住原手数。对策:把“手数上限”锁定为计算结果,止损变远就必须减仓。</li> <li>失败信号:连续亏损后你提高单笔风险比例。对策:引入阶梯降风险规则,例如连亏 3 笔风险减半,连赢 5 笔再恢复。</li> </ul> <h2 id="tools-checklists-and-comparison">工具清单与场景对比表</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>外汇主流货币对(如 EUR/USD)</td> <td>规则化趋势跟随、日内波段</td> <td>中等(点值易算但易忽略新闻跳空)</td> <td>只按点数设仓位,没把账户币种换算写进点值</td> </tr> <tr> <td>黄金(XAU/USD)</td> <td>事件驱动与波动率交易</td> <td>较高(波动扩张快、滑点明显)</td> <td>止损按“心理整数位”,导致止损过近频繁被扫</td> </tr> <tr> <td>美股指数差价合约(如 US500)</td> <td>日内结构交易、趋势突破</td> <td>中高(开盘时段波动与跳价)</td> <td>忽视开盘滑点与缺口,仓位按常态时段计算</td> </tr> <tr> <td>加密永续合约(如 BTC 永续)</td> <td>高波动环境下的短线</td> <td>高(杠杆与强制减仓机制叠加)</td> <td>用杠杆倍数代替风险控制,导致爆仓概率上升</td> </tr> <tr> <td>期货(如原油/利率类)</td> <td>专业化对冲与宏观交易</td> <td>中高(合约乘数固定但跳空风险显著)</td> <td>误读合约乘数或最小跳动价位,计算出错误风险金额</td> </tr> </table> <h2 id="advanced-risk-controls-2026">2026 的进阶风险控制:波动率、相关性与组合层面</h2> <p>当你已经能稳定做到“单笔风险恒定”,下一步是承认现实:市场不是独立同分布。你可能同时持有多个高度相关的头寸,看似每笔只冒 1% 风险,实际上组合风险远超 1%。</p> <p>这里可以引入三个进阶概念:</p> <ul> <li>波动率调整仓位:用 ATR 或历史波动率做止损距离或风险系数,让高波动期自动减仓。</li> <li>相关性与净敞口:同方向的相关品种同时开仓时,把它们当作一个组合来计算总风险。</li> <li>风险预算:给不同策略分配风险额度,例如趋势策略 60%、均值回归 40%,避免同一市场状态下集体失效。</li> </ul> <p>根据 2024 年国际货币基金组织(IMF)关于金融稳定与杠杆风险的相关研究,在压力阶段,资产相关性往往上升,分散效果下降。这意味着你越依赖“多开几个品种分散”,越要在压力场景下做更保守的组合层面减仓。</p> <p>另外,2025 年一些行业研究(包括面向企业风险管理与数据驱动决策的机构报告)强调:将规则写进流程与工具,比培训“更自律”更可靠。落到交易上,就是把仓位计算与下单前置绑定,并把最大日亏、最大周亏设为不可突破的风险闸门。</p> <p>如果你想把组合风险也纳入统一口径,建议把每笔交易的计算结果与账户的日/周风险预算关联起来:当日已亏达到阈值,就停止开新仓;当组合净敞口过于集中,就对新增仓位做折扣系数,而不是继续按单笔公式“机械下单”。</p> <h2 id="conclusion">Conclusion</h2> <p>頭寸大小計算器真正解决的问题不是“怎么下更大的单”,而是“怎么在不确定性里持续活着”。当你把风险金额固定、把止损距离真实化、把点值换算标准化,你的交易会从情绪驱动变成流程驱动。很多人把注意力放在入场技巧,但长期曲线往往由仓位与风险闸门决定。</p> <p>zfx-online 推荐的下一步行动很具体:第一,用 <a href="https://www.zfx-online.com/">頭寸大小計算器</a> 固定单笔风险为账户权益的 0.5% 到 1%,连续执行至少 30 笔并记录实际最大亏损;第二,设置最大日亏为单笔风险的 3 倍,触发即停止交易并复盘;第三,每周核对一次“计算亏损 vs 实际亏损”的偏差,如果偏差长期超过 15%,下调风险比例或增加滑点缓冲。</p> <h2 id="references">References</h2> <p>BIS(国际清算银行),2023-2024:关于市场流动性、波动与压力期价格跳跃风险的研究综述,为本文“滑点与跳空缓冲”提供依据。</p> <p>IMF(国际货币基金组织),2024:关于金融稳定、杠杆与压力期相关性上升的分析,为本文“组合风险与分散失效”提供背景。</p> <p>行业研究与企业风险管理报告(2025):强调流程化与工具化规则执行的有效性,为本文“将仓位计算嵌入交易流程”提供方法论支撑。</p> <h2 id="faq">FAQ</h2> <h3>頭寸大小計算器适合哪些交易者使用?</h3> <p>只要你的交易存在止损或最大可承受亏损,就适合使用。新手用它避免“一笔致命”,有经验的交易者用它统一不同品种的风险口径,并在波动变化时自动调整仓位。</p> <h3>如果我不设止损,还能计算仓位吗?</h3> <p>可以用“账户最大可承受回撤”做粗略上限,但精度会很差,也更容易在跳空时出现超预期亏损。更稳妥的做法是先定义结构止损或波动率止损,再计算仓位,否则你无法把风险金额锁定在可控范围。</p> <h3>为什么我按公式算了仓位,实际亏损还是更大?</h3> <p>最常见原因是滑点、跳空或成交延迟导致止损成交价劣于预期,其次是点值/合约乘数或账户币种换算错误。解决方式是加入滑点缓冲、避开低流动性时段,并用交易日志统计“计算值与实际值”的长期偏差后再校准参数。</p> <h3>我可以用加仓摊薄成本来替代仓位控制吗?</h3> <p>不建议把摊薄当作默认策略,因为它会在趋势行情里放大损失,并让组合风险瞬间失控。如果你确实使用分批进场,仍应把“总风险金额”锁定在同一上限内:后续加仓只能来自更紧的止损或更小的新增仓位。</p> <h3>单笔风险比例越小越好吗?</h3> <p>不一定。过小会让你在合理止损下只能下很小仓位,导致执行变形或频繁放弃交易。更实用的原则是:风险比例要小到能承受策略的正常连亏,同时大到不至于让成本与最小下单单位压垮策略。</p> <h3>同一天内多笔交易,风险该怎么累计计算?</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