2022年4月21日 星期四

EXCEL出現名稱已存在

https://xingzuo69.pixnet.net/blog/post/317996262


問題:

名稱"xxxx"已存在,請按一下是使用該名稱版本,或按否重新命名。

因excel檔案該分頁包含標籤名稱,所以只要在同檔案下複製並建立副本就會出現重複標籤名稱的提示。

解決方法:

1. 按 CTRL+F3 將名稱管理員裡的名稱刪除即可。

2. 如果還是不行,就可能是有隱藏標籤名稱的關係造成。

3. 按 ALT+F11,進入Visual basic編輯器或點選 開發人員→Visual Basic。
   (如果無法開啟,請點此參考教學)
01.png

4. 選取有問題的分頁名稱,按 CTRL+F3,開啟即時運算並輸入 for each n in names : n.visible = true : next

註解 2020-01-11 230725-2.png
註解 2020-01-11 230726.png

5. 點選EXCEL圖示回編輯頁面。
註解 2020-01-11 230725.png


6. 點選公式→名稱管理員。
註解 2020-01-12 135520.png

7. 刪除全部內容既可。
註解 2020-01-11 231015.png

2022年4月4日 星期一

ANSI escape code

 These are ANSI control-code escape sequences that are transmitted when various non alphanumeric keys are pressed on a "terminal" keyboard.

\e means the ASCII "ESCAPE" character (octal 033 hex 1B decimal 27). Which is part of a command sequence introduction (CSI).

Escape [ 2 ~ is a character sequence transmitted when you press the key labelled "Insert" on a VT220 (or later) terminal.

Many of these conventions have been adopted in software such as xterm and Linux consoles / shells - often extended in various, sometimes incompatible ways.

The use of these sequences in bash's READLINE function is described in the man pages for readline

       In  the  second  form,  "keyseq":function-name or macro, keyseq differs
       from keyname above in that strings denoting an entire key sequence  may
       be  specified  by  placing the sequence within double quotes.  Some GNU
       Emacs style key escapes can be used, as in the following example,  but
       the symbolic character names are not recognized.

          "\C-u": universal-argument
          "\C-x\C-r": re-read-init-file
          "\e[11~": "Function Key 1"

To get a list of which escape sequences correspond to which keyboard-keys, you can use a command such as infocmp -L -1 or infocmp -L -1 xterm

BASH rc

========================================================================
= .bashrc
========================================================================
#Colors for 'man' pages
export LESS_TERMCAP_mb=$'\033[01;31m' # begin blinking
export LESS_TERMCAP_md=$'\033[01;38;5;74m' # begin bold
export LESS_TERMCAP_me=$'\033[0m' # end mode
export LESS_TERMCAP_se=$'\033[0m' # end standout-mode
export LESS_TERMCAP_so=$'\033[38;5;246m' # begin standout-mode - info box
export LESS_TERMCAP_ue=$'\033[0m' # end underline
export LESS_TERMCAP_us=$'\033[04;38;5;146m' # begin underline

#EX: PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
#        yulin@WNC:/work

# Add git branch if its present to PS1 
GitBranch()
{
    git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/(\1)/'
}

if [ "$color_prompt" = yes ]; then 
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[01;31m\]$(GitBranch)\[\033[00m\]\$ ' 
else 
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w$(GitBranch)\$ ' 
fi



========================================================================
= .screenrc (/etc/input.rc)
========================================================================


========================================================================
= .inputrc (/etc/input.rc)
========================================================================
# Arrow UP/DOWN to triverse matched history inputs.
"\e[A": history-search-backward
"\e[B": history-search-forward
# HOME/END to move cursor to beginning/end of a line.
"\e[1~": beginning-of-line
"\e[4~": end-of-line


"\e[1~": beginning-of-line
"\e[4~": end-of-line
“\e[5~”: history-search-backward
“\e[6~”: history-search-forward
"\e[3~": delete-char
"\e[2~": quoted-insert
"\e[5C": forward-word
"\e[5D": backward-word
"\e\e[C": forward-word
"\e\e[D": backward-word