[小调查]你为什么折腾emacs/泡emacs-china?

能在 terminal 下用的正经编辑器就两个…

这位仁兄专业造轮子...

Second Climacs is an Emacs-like editor written entirely in Common Lisp. It is called Second Climacs because it is a complete rewrite of the Climacs text editor.

我在一个比较火的emacs视频下面看到第一名的评论是,

  • 上午:tweaking productivity tools
  • 下午:configure emacs
  • 天黑了快下班了:try to ignore office noise and do work

他之前的简介写着他没有Chinese input method。说起来 @MaskRay 的博客显示他是大陆的,但是他在论坛回帖不但用繁体而且用词风格也是台湾风。Anyway,社区leader @LdBeth 曾经说过:

鸟子大了什么林都有

1 个赞

nano好用不?

我觉得也是,每天先list-packages然后更新,更新完了换theme,然后就开始想有什么能改的配置,干活都放到最后了

1 个赞

nano,jed,uemacs, aee,说实话比起这两个都不怎么样

从learning curve和功能的比率上看 nano之类的还不错。现在git都把它当默认编辑器了

遇到这种情况该怎么办,还觉得emacs有一堆要学就烦躁了

來用 Forth 啊。


正在写的小游戏的一部分。

Hanafuda Query

create MonthTable
,"  Jan"
,"  Feb"
,"  Mar"
,"  Apr"
,"  May"
," June"
," July"
,"  Aug"
," Sept"
,"  Oct"
,"  Nov"
,"  Dec"

: looktable ( n table  -- )
  swap cells + @c count type ;
: printmonth ( n -- )
  12 min 1- MonthTable looktable ;

create NameTable
," Crane   " ," Red Ribb"
," Nightale" ," Red Ribb"
," Curtain " ," Red Ribb"
," Cuckoo  " ," Ribbon  "
," Yatsuhas" ," Ribbon  "
," Buterfly" ," Blue Rib"
," Boar    " ," Ribbon  "
," Moon    " ," Goose   "
," Sake Cup" ," Blue Rib"
," Deer    " ," Blue Rib"
," Ono No M" ," Swallow "
," Phoneix " ," Plain 2 "

: printplain ( rank -- )
  ." Plain " . ;

: printname ( rank month -- )
  over 2 >
  if \ For Special case of Nov
    11 = \ rank flag
    over 3 = and \ rank flag
    if ." Ribbon  " drop
    else printplain
    then \ --
  else 1- 2* + 1- 23 min \ Safe
       NameTable looktable
  then ;

create TypeNTable
3 , 1 , 0 , \ Jan
2 , 1 , 0 ,
3 , 1 , 0 ,
2 , 1 , 0 , \ April
2 , 1 , 0 ,
2 , 1 , 0 ,
2 , 1 , 0 , \ July
3 , 2 , 0 ,
4 , 1 , 0 ,
2 , 1 , 0 , \ Oct
3 , 2 , 0 ,
3 , 0 , 0 ,
\ 1   2   3   4

create TypeTable
," [Plain]" ," [Ribbon]" ," [Seed]"
\      0            1          2
," [Light]" ," [Seed/Plain]"
\      3            4

: 3* ( n -- 3n )
  3 * ;
: printtype ( rank month -- )
  over 4 =
  if drop drop 0
  else 1- 3* + 1- 35 min \ safe
       TypeNTable swap th @c
  then TypeTable looktable ;

: printcard ( rank month -- )
  dup printmonth \ rank month
  space
  2dup printname space
  printtype ;

\ Tests
2 8 printcard cr
2 1 printcard cr
3 4 printcard cr
1 12 printcard cr
>> 0:~/P/P/handafuda $ 4th cx monthtable.fth                         << 23:05 <]
4tH library v3.62 - Copyright 1994,2014 J.L. Bezemer
 Aug Goose    [Seed]
 Jan Red Ribb [Ribbon]
 Apr Plain 3  [Plain]
 Dec Phoneix  [Light]

真够闲的...

有这闲工夫帮我救一下命.

mint 18 不小心手贱, 装了个不该装的驱动:

sudo apt-get install nvidia-331

现在apt状态异常.被卡住了.

怎么手动卸掉这个包?

日志文件里面的错误:

(cat /dev/null; echo kernel//var/lib/dkms/nvidia-340/340.104/build/nvidia.ko;) > /var/lib/dkms/nvidia-340/340.104/build/modules.order

为什么显卡驱动能炸到包管理器?

1 个赞

貌似这个显卡驱动安装的时候需要编译内核的什么东西,结果编译的时候出错了,然后就一直卡在出错的地方.

直接 ps 看下以后 kill

不是编译进程卡住了,而是编译错误卡住了apt的状态, apt记录中有一个包出错,每次都尝试先重新处理这个有错误的包

apt purge无法处理了, 下面是完整的出错过程

gxy@local:~/Desktop$ sudo apt purge nvidia

  • [sudo] password for gxy:

  • Reading package lists… Done

  • Building dependency tree

  • Reading state information… Done

  • Package ‘nvidia’ is not installed, so not removed

  • The following packages were automatically installed and are no longer required:

  • compiz-core compiz-plugins-default libcompizconfig0 libdecoration0 libllvm5.0 libllvm5.0:i386 libopenshot14 python-compizconfig

  • Use ‘sudo apt autoremove’ to remove them.

  • 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  • 1 not fully installed or removed.

  • After this operation, 0 B of additional disk space will be used.

  • Setting up nvidia-340 (340.104-0ubuntu0.16.04.1) …

  • update-initramfs: deferring update (trigger activated)

  • update-initramfs: Generating /boot/initrd.img-4.13.0-45-generic

  • INFO:Enable nvidia-340

  • DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here

  • DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude

  • DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad

  • Removing old nvidia-340-340.104 DKMS files…

  • -------- Uninstall Beginning --------

  • Module: nvidia-340

  • Version: 340.104

  • Kernel: 4.13.0-45-generic (x86_64)


  • Status: Before uninstall, this module version was ACTIVE on this kernel.

  • nvidia_340.ko:

    • Uninstallation
    • Deleting from: /lib/modules/4.13.0-45-generic/kernel/drivers/char/drm/
    • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
  • nvidia_340_uvm.ko:

    • Uninstallation
    • Deleting from: /lib/modules/4.13.0-45-generic/kernel/drivers/video/
    • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
  • depmod…

  • DKMS: uninstall completed.


  • Deleting module version: 340.104

  • completely from the DKMS tree.


  • Done.

  • Loading new nvidia-340-340.104 DKMS files…

  • First Installation: checking all kernels…

  • Building for 4.13.0-45-generic and 4.15.0-24-generic

  • Building for architecture x86_64

  • Building initial module for 4.13.0-45-generic

  • Done.

  • nvidia_340:

  • Running module version sanity check.

    • Original module
    • No original module exists within this kernel
    • Installation
    • Installing to /lib/modules/4.13.0-45-generic/kernel/drivers/char/drm/
  • nvidia_340_uvm.ko:

  • Running module version sanity check.

    • Original module
    • No original module exists within this kernel
    • Installation
    • Installing to /lib/modules/4.13.0-45-generic/kernel/drivers/video/
  • depmod…

  • DKMS: install completed.

  • Building initial module for 4.15.0-24-generic

  • Error! Bad return status for module build on kernel: 4.15.0-24-generic (x86_64)

  • Consult /var/lib/dkms/nvidia-340/340.104/build/make.log for more information.

  • dpkg: error processing package nvidia-340 (–configure):

  • subprocess installed post-installation script returned error exit status 10

  • Processing triggers for libc-bin (2.23-0ubuntu10) …

  • Processing triggers for initramfs-tools (0.122ubuntu8.11) …

  • update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

  • Errors were encountered while processing:

  • nvidia-340

  • E: Sub-process /usr/bin/dpkg returned an error code (1)

我已经找到文件位置,手工移走有问题的文件,准备重启了,如果很久都没有回来,那就是机器彻底挂了....

祝福我吧...

回来了...

世界还是那么美好....

最终的解决方案是把/var/lib/dpkg/info 下面的有问题的包的文件移走就可以了.

我入坑已经半年了,这半年的时间花了至少得有300小时的时间。感觉这个东西怎么说呢,性价比真是不高。总是遇到各种问题,为了1个工具的问题话费太多时间,有成就感的同时也觉得有点浪费。

是的,而且我发现非常有毒的是给各种 elisp 包(还有spacemacs!)提交 PR,三刷两刷一个小时就过去了