{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 我想做一个坏孩纸 的问题《Can rlwrap use a wrapped command's own TAB com》','https://www.manongdao.com/q-1196236.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I want to use rlwrap with a custom erlang repl.
It works perfectly if I run it as "rlwrap -a myrepl".
The problem is that myrepl has builtin tab completion which gets trampled by rlwrap.
I want to make rlwrap to release the TAB key
相关问题
- Google places autocomplete suggestion without coun
- Is “new” in Erlang part of the official standard a
- how to create a keep-alive process in Erlang
- How to not have Gradle quit Scala's REPL immed
- ejabberd and Erlang installation with lager_transf
相关文章
- Set the z-index value of a jQuery autocomplete inp
- How do I modify a record in erlang?
- Check active timers in Erlang
- How to disable autocomplete in address fields for
- undefined function maps:to_json/1
- How to convert datetime() to timestamp() in Erlang
- Clear text box in Jquery Autocomplete after select
- Jquery UI autocomplete - Unwanted triggering due t
Rlwrap is cute. But in Erlang, it only offers persistent history while breaking erl's tab completion.
The fundamental issue is Erlang's erl REPL is just old and busted, and doesn't follow normal *nix conventions. Furthermore, they refuse to fix it because of fear of random, grouchy sysadmins whom can't accept any changes. No amount of rlwrap "duct-tape" hacks can fix a poor UX REPL.
It would be better (though significantly more work) to write a REPL from scratch like pry/ipython/etc. that does configurable color, tab completion, persistent history, paging, CLI observer, plugins, etc.
Rlwrap shines on programs with primitive shells.
You can't use
rlwrap's line editing/history and your repl's TAB completion at the same time.rlwrapprovides line editing, history and (very simple) completion for commands that don't have it. A command that has something as fancy as TAB completion shouldn't needrlwrapto do its line editing, should it?The
-a(--always-readline) option is a rather crude way to substitute rlwrap's line editing behaviour for that of your command. It is primarily meant for commands that have a very simple line editor, without e.g. command historyIf you want to use the
-aoption because you preferrlwrap's fanciness (like persistent history, or coloured prompts) to your command's (like TAB completion), go ahead, but it is impossible to pick some fanciness of one and keep some of the other.This is the (small) price programs (and their users) have to pay for avoiding the
readlinelibrary and the GPL license that comes with it.Hans (
rlwrapauthor)Edit (April 2017):
In many cases it will be possible to use a filter to restore completion. See A node shell based on readline for an example of this.