Re: Should GNU APL write to .apl.history when invoked with the --eval option?

[Dr . Jürgen Sauermann]

    Hi,
    
    IMHO it would be somewhat odd if the history were dependent on
    command
    line options. Instead you can set the file where the history is
    written in one of
    the the preferences files. The default is .apl.history (i.e. in the
    current directory).
    
    If you need multiple places for the history under different
    circumstances then
    you can use profiles in the preferences file to select one of them.
    Setting it to
    /dev/nul should disable writing of the log (or else maybe
    READLINE_HISTORY_LEN = 0
    
    Best Regards,
    Jürgen

On 2/4/24 08:26, Russtopia wrote:

Preface: this is somewhat trivial.

Context: I was logged into a remote server, doing some filesystem space calculations using GNU APL as my preferred shell 'calculator', using the --eval option, while located in a directory where writing is restricted for regular users (here the /ext0 volume):

--

russtopia@tripe /ext0 $ apl --eval "+/ 12 552 14 20 262 254 7.2"
1121.2

Cannot write history file .apl.history: Permission denied

---

Since --eval seems intended to enable use of the APL interpreter outside of any workspace, might it be better to avoid writing to .apl.history when this flag is specified?