Re: comint / gdb file name completion with spaces in its path

[Nick Roberts]

 > > That's because it's parsed in gud-common-init with split-string,  
 > > not in a
 > > shell.
 > 
 > A shell with completion would automatically quote the filename if  
 > that is necessary. Maybe this can be done as well when interactively  
 > prompting for the gdb arguments?
 > The tokenizer you mention would have to be able to deal with quoted  
 > arguments.

They could be quoted via TAB by setting comint-file-name-quote-list
appropriately as below.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


*** gud.el      24 May 2006 09:24:48 +1200      1.108
--- gud.el      29 May 2006 13:19:52 +1200      
*************** required by the caller."
*** 645,651 ****
    :inherit minibuffer-local-map)
  
  (defun gud-query-cmdline (minor-mode &optional init)
!   (let* ((hist-sym (gud-symbol 'history nil minor-mode))
         (cmd-name (gud-val 'command-name minor-mode)))
      (unless (boundp hist-sym) (set hist-sym nil))
      (read-from-minibuffer
--- 645,652 ----
    :inherit minibuffer-local-map)
  
  (defun gud-query-cmdline (minor-mode &optional init)
!   (let* ((comint-file-name-quote-list '(32))
!        (hist-sym (gud-symbol 'history nil minor-mode))
         (cmd-name (gud-val 'command-name minor-mode)))
      (unless (boundp hist-sym) (set hist-sym nil))
      (read-from-minibuffer